Related
WARNING!!!
Don't use ROM Manager!!!!
It'll brick your phone!!!!
Don't even think of installing ROM Manager on your phone. All it's gonna do is brick your phone....
So my advice is, abstain from using ROM Manager until they officially support our phone.
Till then, use the unofficial port of Clockwork Recovery Mod by tj_style.
the complete package is also attached with this post.
DO NOT FLASH IT ON FROYO!!!
If you need any further assistance, please continue the discussion here.
Download CWM.ZIP here
Edit (17-8-12)
It seems like adityam533 has found a method to make ROM manager work on G-Fit.
For further details, go >>>here<<<
yes thanks for the heads up. anyway, ROM manager does recognize and uploads a rom for Galaxy Mini which is not for Fit. The newest Rom Manager can detect the ported CWM recovery so it might be seeing our phone as Galaxy Mini. Installing from it could brick your phone in the process. Last night I did flashed the Touch enabled CWM recovery thru CWM Recovery Mode from the other post and it worked fine.
Yes... I had corrupted my motherboard...last week
Aspire said:
WARNING!!!
Don't use ROM Manager!!!!
It'll brick your phone!!!!
Don't even think of installing ROM Manager on your phone. All it's gonna do is brick your phone....
So my advice is, abstain from using ROM Manager until they officially support our phone.
Till then, use the unofficial port of Clockwork Recovery Mod by tj_style.
the complete package is also attached with this post.
DO NOT FLASH IT ON FROYO!!!
If you need any further assistance, please continue the discussion here.
Download CWM.ZIP here
Click to expand...
Click to collapse
Yes... I had corrupted my motherboard... My phone went dead after tapping on backup rom in rom manager. Will never use rom manAger in future
Sent from my GT-S5670 using XDA
Sent from my GT-S5670 using XDA
It is true. Britch S5670 was due to this program. The guarantee, they did change the motherboard.
Aspire said:
WARNING!!!
Don't use ROM Manager!!!!
It'll brick your phone!!!!
Don't even think of installing ROM Manager on your phone. All it's gonna do is brick your phone....
So my advice is, abstain from using ROM Manager until they officially support our phone.
Till then, use the unofficial port of Clockwork Recovery Mod by tj_style.
the complete package is also attached with this post.
DO NOT FLASH IT ON FROYO!!!
If you need any further assistance, please continue the discussion here.
Download CWM.ZIP here
Click to expand...
Click to collapse
when will our phone be supported mini already is bt not us
Sent from my GT-S5670 using XDA
alaric.m said:
when will our phone be supported mini already is bt not us
Sent from my GT-S5670 using XDA
Click to expand...
Click to collapse
Even the supported devices have been bricked because of it...ask about it in the mini and ace forum...
We already have a good enough way to flash cwm...
Typed on a small touchscreen
hello, I am the victim fell from the program and can tell me what else our need me to do with my device, should be replaced any part or program only ?
faatoos said:
hello, I am the victim fell from the program and can tell me what else our need me to do with my device, should be replaced any part or program only ?
Click to expand...
Click to collapse
IS THE PHONE booting ?
udit.kumar said:
IS THE PHONE booting ?
Click to expand...
Click to collapse
No bro :S nothing :S i cant bay new phone now :S damn :....
faatoos said:
No bro :S nothing :S i cant bay new phone now :S damn :....
Click to expand...
Click to collapse
warranty ?
hey guys
don't worry
ROM manager is working like a charm for our FIT
look
here,
http://forum.xda-developers.com/showthread.php?t=1827750
to get ROM manager working!!!
tbh i personally find ROM manager useless anyway :/
i'll add that though.
abhinav2196 said:
Yes... I had corrupted my motherboard... My phone went dead after tapping on backup rom in rom manager. Will never use rom manAger in future
Sent from my GT-S5670 using XDA
Sent from my GT-S5670 using XDA
Click to expand...
Click to collapse
Did the same f****** thing... But with my Mini a year ago. Same story. Flashed CWM and I pressed Nandroid Backup... LAst thing my poor Mini did. Ever :'(
Aspire said:
tbh i personally find ROM manager useless anyway :/
i'll add that though.
Click to expand...
Click to collapse
Do you know how to revive the bricked phone from used rom manager?
Thanks
wm_shi said:
Do you know how to revive the bricked phone from used rom manager?
Thanks
Click to expand...
Click to collapse
Currently impossible, the only way to fix it is getting it to Samsung to replace the Motherboard...
Did this with my phone, yay for warranty =)
AXAz0r said:
Currently impossible, the only way to fix it is getting it to Samsung to replace the Motherboard...
Did this with my phone, yay for warranty =)
Click to expand...
Click to collapse
But I still can't understand why rom manager can destroy the motherboard.
If this is the truth, any other rooted android program can do such things to destroy your phone.
I don't think the phone factory might do such a design.
It's too dangerous to use this phone!
wm_shi said:
But I still can't understand why ROM manager can destroy the motherboard.
If this is the truth, any other rooted android program can do such things to destroy your phone.
I don't think the phone factory might do such a design.
It's too dangerous to use this phone!
Click to expand...
Click to collapse
Well ROM Manager doesn't, flashing the CWM Recovery with it bricks the phone, my theory is that some of the data gets lost, or maybe the ROM Manager just can't write to the RFS partition, or doesn't support it completely, at least the one on our phone, it formats the whole phone, but that's only my stupid theory =)
AXAz0r said:
Well ROM Manager doesn't, flashing the CWM Recovery with it bricks the phone, my theory is that some of the data gets lost, or maybe the ROM Manager just can't write to the RFS partition, or doesn't support it completely, at least the one on our phone, it formats the whole phone, but that's only my stupid theory =)
Click to expand...
Click to collapse
Yes, I also think that maybe the cwm recovery bricked my phone, maybe some of the data lost, maybe ....
But why odin can't overwrite all of the mistakes?
There must be somthing that odin can't overwrite but rom manager can write.
What's this?
wm_shi said:
Yes, I also think that maybe the cwm recovery bricked my phone, maybe some of the data lost, maybe ....
But why odin can't overwrite all of the mistakes?
There must be somthing that odin can't overwrite but rom manager can write.
What's this?
Click to expand...
Click to collapse
it cant undo the mistakes because the "ARM11BOOT.img" is corrupted, basicly, you cant even turn on your phone, at all, so that means no download mode
Just curious if it works on our phones. I'd really love to have dual boot options for cm9 and sense.
iheartn1 said:
Just curious if it works on our phones. I'd really love to have dual boot options for cm9 and sense.
Click to expand...
Click to collapse
Non, never tried but I'm not sure I'm understanding what that app does...
kipox said:
Non, never tried but I'm not sure I'm understanding what that app does...
Click to expand...
Click to collapse
It adds the ability to multi boot. Kind of like your computer being able to run windows and linux, this lets our phones run up to 5 different roms
iheartn1 said:
It adds the ability to multi boot. Kind of like your computer being able to run windows and linux, this lets our phones run up to 5 different roms
Click to expand...
Click to collapse
so did any1 test it meanwhile?
b0mb said:
so did any1 test it meanwhile?
Click to expand...
Click to collapse
Yeah I've tried it once, didn't work for me.. for a moment i was afraid i had bricked my phone, so i would not recommend it. but I'm not sure that I've done everything correctly
philipp1996 said:
Yeah I've tried it once, didn't work for me.. for a moment i was afraid i had bricked my phone, so i would not recommend it. but I'm not sure that I've done everything correctly
Click to expand...
Click to collapse
I just gave it a shot -- I added all the stuff manually, but would get an error that it was unable to download the files. I ended up using a titanium backup to load the data and after that it would launch. However, when I tried installing a ROM, I would get an error that it was unable to create a new boot.img. I might try a different ROM to see if that works.
please let us know if it worked!
Hello everyone, i have learned to port ubuntu touch on other device for a few days, and this is the first time for me to port a ubuntu touch rom.
This rom is based on phablet-20130303-cm_mb526.zip for defy, and i added some milestone2's bin, lib, bootmenu and etc in it so that it could run on our milestone2.
Don't get happy yet. As you know, i'm new here and i even don't have this phone(i have d2g, it doesn't have any cm10.1+ rom). so this rom is just a homework for me to check whether i could port ubuntu touch or not. i don't know what will happen after you flash this rom, so please make sure that you can fix your phone by bootmenu or rsd.
how to flash it?
1. Backup your current Rom.
2. Download the Milestone2 Mini-Android base for Ubuntu Touch and place it on your device:
https://drive.google.com/file/d/0Bylduk-LZybUelp6SGV0ZFlvWGM/view?usp=sharing
3. Download the Touch Preview Filesystem .zip and place it on your device:
http://www.mediafire.com/?dg5bf836ohvioot
4. Wipe all (data/cache, dalvik cache)
IMPORTANT:
5. Install the armhf package FIRST, and then the phablet-20141025-ubuntutouch_milestone2.zip SECOND.
thanks for @lukasz124 finding this problem！
6. Reboot and See whether your device can boot or not.(it will cost about 5-10 minutes for your device to boot if this rom could work, and no bootanimation!)
7a. To switch off your phone remove the battery manually
7b. To return back to android reboot back into recovery and reinstall or restore your rom.
8. If your rom is not booting it could be due to the ext 4 format of /data so go into stock recovery and wipe all (data/cache, dalvik cache), reboot, reinstall.
and that is all. i can't wait to see whether this rom can work or not!
thanks MYHK-to help me porting this rom kayant-for his defy ubuntu touch rom e-mars-for his porting work on cm
Tks, Anyone out there already tested? Has some print? Do you know if wifi, usb, etc, is working? Thanks
shulinbao said:
Don't get happy yet. As you know, i'm new here and i even don't have this phone(i have d2g, it doesn't have any cm10.1+ rom). so this rom is just a homework for me to check whether i could port ubuntu touch or not.
Click to expand...
Click to collapse
If this works you can have my phone. It's kinda crappy, but does the job.
Could not install the ROM.
Kiil said:
Could not install the ROM.
Click to expand...
Click to collapse
THANK YOU VERY MUCH FOR YOUR TESTING. there are two .zip file to flash, please tell me which .zip file could not install, thank you!
No problem. I could not make either one to work. Tried CWM and "install zip file", is this the correct procedure?
Kiil said:
No problem. I could not make either one to work. Tried CWM and "install zip file", is this the correct procedure?
Click to expand...
Click to collapse
thank you for your testing, it's a really strange problem. the Mini-Android base is port from cm11- milestone2 by e-mars and the Touch Preview Filesystem is official. i don't know whether my sign tool is ok or not, and i don't know if the script works well. you know is hard for me to solve any problem, but i always keep on trying it.
maybe i have to find others to keep on this project, i think if someone have any skill, it's not hard for him to port it.
shulinbao said:
thank you for your testing, it's a really strange problem. the Mini-Android base is port from cm11- milestone2 by e-mars and the Touch Preview Filesystem is official. i don't know whether my sign tool is ok or not, and i don't know if the script works well. you know is hard for me to solve any problem, but i always keep on trying it.
maybe i have to find others to keep on this project, i think if someone have any skill, it's not hard for him to port it.
Click to expand...
Click to collapse
I disabled signature checking, so it is not that. Unfortunately I'm not familiar with logging CWM otherwise you would get a nice log : D Yeah, it seems like a nice project, hopefully some people will join, droid/milestone series seems like a perfect one for Ubuntu.
Hi!! Thanks for trying to bring Ubuntu to our Milestone 2!
I've tried to install, but the system goes on infinite reboot. I think I'm doing something wrong.
yuriaps said:
Hi!! Thanks for trying to bring Ubuntu to our Milestone 2!
I've tried to install, but the system goes on infinite reboot. I think I'm doing something wrong.
Click to expand...
Click to collapse
How did you install it? Probably not through CWM?
yuriaps said:
Hi!! Thanks for trying to bring Ubuntu to our Milestone 2!
I've tried to install, but the system goes on infinite reboot. I think I'm doing something wrong.
Click to expand...
Click to collapse
THANK YOU FOR YOUR HELP! maybe i need log............................ i had a talked with myhk yesterday, he have been porting ubuntu touch for a year, and he told me that the way of my porting work seems right...
shulinbao said:
THANK YOU FOR YOUR HELP! maybe i need log............................ i had a talked with myhk yesterday, he have been porting ubuntu touch for a year, and he told me that the way of my porting work seems right...
Click to expand...
Click to collapse
It's probably us, then : D
What kind of methods would you use to flash it? Is cwm good enough or do you need adb?
Kiil said:
It's probably us, then : D
What kind of methods would you use to flash it? Is cwm good enough or do you need adb?
Click to expand...
Click to collapse
thank you for your helping!
i think cwm is ok, the log will only be used to find what cause the problem, and that will cost a long time... maybe after the android5.0 of milestone2 come out. the android 5.0 of defy came out yesterday in China and Russia, it won't take a long time to wait for the android 5.0 of miletone2.
but ubuntu touch of milestone2 is different..... as you know i don't have milestone2, it should take a long time in printing logs over and over again to find problem.
Did anyone install this?
I also got infinite reboot
I could donate you my kind of old milestone 2. Depends on postal charges, tho. Pm me, if you're interested.
I am using moto g3 x1550. A few months ago my scree was broken and make it replaced but it was not original. But it work perfect on L.P (5.0) based ROM but when I install M.M (6.0) based ROM touch does not work as from the starting from the language setup but only volume and power key are working and also display but not touch...
Plzzz help me up.
If your screen isnt original then chances are your device will be rejected to be serviced at moto center.
edit : http://forum.xda-developers.com/showpost.php?p=66002023&postcount=1262 try flashing these zip files and see if your touch screen is back.
Else you can try downgrading to lollipop or reflashing stock MM images and see if your touch screen is working. Use this linkhttp://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 to flash stock images. Note: data loss might occur backup data that is important.
vimjam said:
If your screen isnt original then chances are your device will be rejected to be serviced at moto center.
edit : http://forum.xda-developers.com/showpost.php?p=66002023&postcount=1262 try flashing these zip files and see if your touch screen is back.
Else you can try downgrading to lollipop or reflashing stock MM images and see if your touch screen is working. Use this linkhttp://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 to flash stock images. Note: data loss might occur backup data that is important.
Click to expand...
Click to collapse
Is it safe. I mean that my phone could get had brick or permanently touch not work after flashing that file.
Sorry for bad English?
Piyush Garg said:
Is it safe. I mean that my phone could get had brick or permanently touch not work after flashing that file.
Sorry for bad English
Click to expand...
Click to collapse
hmm this can also be a hardware problem as the touchscreen in not generic and we do not know how it will react to the drivers, so noting cannot be guaranteed. Your best bet is to take a leap of faith and flash the zip, if it fails you can always return to lollipop roms.
That flashable zip just replaces touch drivers not the entire rom. Besides that flashable zip was created by Alberto97 who brought us CM13 so i highly doubt that flashable zip will brick your phone.
But none the less if you truly want a fail safe procedure your best bet is moto service.
p.s no one at xda is responsible for anything happening to any device as this is a community not a paid service where we are responsible for our work.
vimjam said:
hmm this can also be a hardware problem as the touchscreen in not generic and we do not know how it will react to the drivers, so noting cannot be guaranteed. Your best bet is to take a leap of faith and flash the zip, if it fails you can always return to lollipop roms.
That flashable zip just replaces touch drivers not the entire rom. Besides that flashable zip was created by Alberto97 who brought us CM13 so i highly doubt that flashable zip will brick your phone.
But none the less if you truly want a fail safe procedure your best bet is moto service.
p.s no one at xda is responsible for anything happening to any device as this is a community not a paid service where we are responsible for our work.
Click to expand...
Click to collapse
Which one should be flashed.
Now I am using cm12.1 so can I flash these zip in it or first I flash cm13 and and flash these zip.
And if pH get brick then will it be hard brick or soft..
thanks :thumbup:
Piyush Garg said:
Which one should be flashed.
Now I am using cm12.1 so can I flash these zip in it or first I flash cm13 and and flash these zip.
And if pH get brick then will it be hard brick or soft..
thanks :thumbup:
Click to expand...
Click to collapse
if it gets bricked it will be soft brick , you can go to twrp wipe & flash cm again. these drivers are for cm13 so you need to flash after cm13 is flashed or along with cm13.
the first zip is to restore to older stable drivers , so flash this first . If the touch screen didn't improve flash the second one to restore to default drivers.
Im facing too.. Try BrokenOS.. No issues in that rom!
vimjam said:
if it gets bricked it will be soft brick , you can go to twrp wipe & flash cm again. these drivers are for cm13 so you need to flash after cm13 is flashed or along with cm13.
the first zip is to restore to older stable drivers , so flash this first . If the touch screen didn't improve flash the second one to restore to default drivers.
Click to expand...
Click to collapse
Same problem touch is not working
After flashing both file..of drivers
Piyush Garg said:
Same problem touch is not working
After flashing both file..of drivers
Click to expand...
Click to collapse
Touch issue is an hardware related problem. Motorola IT say me that IT is an hardware problem exasperated by MM update (and related synaptics drivers).
Imho it is due by bad grounded IC or by the glue used to bind the LCD at motherboard
IMP_IT said:
Touch issue is an hardware related problem. Motorola IT say me that IT is an hardware problem exasperated by MM update (and related synaptics drivers).
Imho it is due by bad grounded IC or by the glue used to bind the LCD at motherboard
Click to expand...
Click to collapse
Yes I had changed my whole screen and it is duplicate.
Is there is any way to solve this problem plzzz plzzz held..
Piyush Garg said:
Yes I had changed my whole screen and it is duplicate.
Is there is any way to solve this problem plzzz plzzz held..
Click to expand...
Click to collapse
yes. Try this
https://www.dropbox.com/s/jemv0yqjf9m25vm/IMG_20160319_154102989.jpg?dl=0
https://www.dropbox.com/s/dc2pgzrc2lcdnf8/IMG_20160319_154042223.jpg?dl=0
IMP_IT said:
yes. Try this
https://www.dropbox.com/s/jemv0yqjf9m25vm/IMG_20160319_154102989.jpg?dl=0
https://www.dropbox.com/s/dc2pgzrc2lcdnf8/IMG_20160319_154042223.jpg?dl=0
Click to expand...
Click to collapse
How to use this
Piyush Garg said:
Yes I had changed my whole screen and it is duplicate.
Is there is any way to solve this problem plzzz plzzz held..
Click to expand...
Click to collapse
Piyush Garg said:
How to use this
Click to expand...
Click to collapse
it's black humour but it also demonstrate that there is an hw problem. If you try to put an aluminium foil in back cover of your moto g the touch issue disappears completely. But it also may modify SAR values, reception etc...
But, I say try it so you can see that problem disappear.
IMP_IT said:
it's black humour but it also demonstrate that there is an hw problem. If you try to put an aluminium foil in back cover of your moto g the touch issue disappears completely. But it also may modify SAR values, reception etc...
But, I say try it so you can see that problem disappear.
Click to expand...
Click to collapse
My problem will disappear or my phone?
IMP_IT said:
it's black humour but it also demonstrate that there is an hw problem. If you try to put an aluminium foil in back cover of your moto g the touch issue disappears completely. But it also may modify SAR values, reception etc...
But, I say try it so you can see that problem disappear.
Click to expand...
Click to collapse
Is this really work..
Piyush Garg said:
Same problem touch is not working
After flashing both file..of drivers
Click to expand...
Click to collapse
Piyush Garg said:
Is this really work..
Click to expand...
Click to collapse
Yes it really work but it s not reccomanded
IMP_IT said:
Yes it really work but it s not reccomanded
Click to expand...
Click to collapse
Why??
Piyush Garg said:
Why??
Click to expand...
Click to collapse
Because can modify SAR values and the exposition of body to EM fields
IMP_IT said:
Because can modify SAR values and the exposition of body to EM fields
Click to expand...
Click to collapse
So what problem would I face
Have u tryed it or saw someone doing this
Piyush Garg said:
So what problem would I face
Have u tryed it or saw someone doing this
Click to expand...
Click to collapse
No problem. I tried this. I 'invented' this lol.
Try once it does not cause anithing except different irradiation by EM fields
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
Device-State:Recovery/Bootloader
Ellipsis 8
QTAQZ3
Vendor:Verizon Wireless
Build:KTO49
4.2KitKat
samson716 said:
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
?
Click to expand...
Click to collapse
You want help with a device but you don't tell us any kind of information about your device, how smart was that? What you need and how to do it can depend on what device model number you have.
Sent from my SM-S903VL using Tapatalk
SORRY
Droidriven said:
You want help with a device but you don't tell us any kind of information about your device, how smart was that? What you need and how to do it can depend on what device model number you have.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3/4.2Jellybean/KTO49
samson716 said:
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3
4.2Kitkat
KTO49
Thanks!
Click to expand...
Click to collapse
samson716 said:
samson716 said:
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3
4.2Kitkat
KTO49
Thanks!
Click to expand...
Click to collapse
are you using stock recovery or a custom recovery?
Click to expand...
Click to collapse
ayu321 said:
samson716 said:
are you using stock recovery or a custom recovery?
Click to expand...
Click to collapse
Stock
Click to expand...
Click to collapse
samson716 said:
ayu321 said:
Stock
Click to expand...
Click to collapse
Can you please tell me that what caused this problem ? what were you doing with the device? flashing roms ?
Click to expand...
Click to collapse
ayu321 said:
samson716 said:
Can you please tell me that what caused this problem ? what were you doing with the device? flashing roms ?
Click to expand...
Click to collapse
No I was literally doing nothing I was actually flashing my Samsung Device at that moment. From what I remember it occurred when I noticed at update to marshmallow updated then rebooted it. Ever since its been in this bootloop! Im not trying to root it put a custom rom on it just want it to function nothing special.
Click to expand...
Click to collapse
samson716 said:
ayu321 said:
No I was literally doing nothing I was actually flashing my Samsung Device at that moment. From what I remember it occurred when I noticed at update to marshmallow updated then rebooted it. Ever since its been in this bootloop! Im not trying to root it put a custom rom on it just want it to function nothing special.
Click to expand...
Click to collapse
You have soft bricked your phone . The only way to fix it is it flash its stock rom. If you are new to this stuff I would suggest you to read this article carefully and if you have any doubts , ask me.
https://www.maketecheasier.com/android-root-custom-recovery-and-roms/
Click to expand...
Click to collapse
samson716 said:
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
Device-State:Recovery/Bootloader
Ellipsis 8
QTAQZ3
Vendor:Verizon Wireless
Build:KTO49
4.2KitKat
Click to expand...
Click to collapse
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a device exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
ayu321 said:
samson716 said:
You have soft bricked your phone . The only way to fix it is it flash its stock rom. If you are new to this stuff I would suggest you to read this article carefully and if you have any doubts , ask me.
https://www.maketecheasier.com/android-root-custom-recovery-and-roms/
Click to expand...
Click to collapse
Okay not sure which Flash tool to use nor get my stock rom I dread to say but i dont think there is one available. Its a generic tablet its made by Quanta. Not sure how to put it in a download mode either I assume ADB is the only way to transfer any files.
Click to expand...
Click to collapse
Your device probably uses SPFlashtool or fastboot.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a deuce exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Its pretty easy to fix a soft bricked device , even if stock rom isnt available , any rom compatible with his device can fix the issue .
ayu321 said:
Its pretty easy to fix a soft bricked device , even if stock rom isnt available , any rom compatible with his device can fix the issue .
Click to expand...
Click to collapse
To be compatible, the ROM typically has to be ported and that usually requires the stock firmware or stock source from the device that the ROM is being ported over to. 99% of the time you can't just flash a ROM from a different model number, even if the CPU is the same, there's quite a bit more to it than that. The android operating system is built for the specific hardware it is installed on, the two devices would have to be exactly the same and have the exact same components, any differences in hardware make he firmwares incompatible.
For this particular device, I doubt the stock firmware or stock source code area available, even if it were, porting another ROM wouldn't be necessary because if it were available it could just be flashed with that instead of porting a ROM.
About the only time a ROM from a different model number can be used without any porting or edits being made is when the devices are exactly the same device just rebranded with a different "name".
But thanks for trying to tell me something that you thought I didn't know, now it seems I've told you something that you didn't know.
Sent from my SM-S903VL using Tapatalk
samson716 said:
ayu321 said:
Okay not sure which Flash tool to use nor get my stock rom I dread to say but i dont think there is one available. Its a generic tablet its made by Quanta. Not sure how to put it in a download mode either I assume ADB is the only way to transfer any files.
Click to expand...
Click to collapse
1.Search for your tablet's root package , download it and move it to your tablet's sd card. Then enter your recovery mode by pressing power button+ Home button+ Volume button at same time for 10sec. Once entered , go to option "apply update from sd card" and select the root package you downloaded. (CONGRATS YOU HAVE ROOTED YOUR PHONE!)
2.Search for your tablet's 'custom recovery' , download it and flash it through odin tool(pc) .
3.Final Step ! BASED ON THE RECOVERY YOU FLASHED THESE STEPS MAY DIFFER , SO REPLY ME IF YOU SUCCEED IN FLASHING CUSTOM RECOVERY
Click to expand...
Click to collapse
ayu321 said:
1.Search for your tablet's root package , download it and move it to your tablet's sd card. Then enter your recovery mode by pressing power button+ Home button+ Volume button at same time for 10sec. Once entered , go to option "apply update from sd card" and select the root package you downloaded. (CONGRATS YOU HAVE ROOTED YOUR PHONE!)
2.Search for your tablet's 'custom recovery' , download it and flash it through odin tool(pc) .
3.Final Step ! BASED ON THE RECOVERY YOU FLASHED THESE STEPS MAY DIFFER , SO REPLY ME IF YOU SUCCEED IN FLASHING CUSTOM RECOVERY
Click to expand...
Click to collapse
Odin is for Samsung devices, not other devices.
The device they are repairing is not a Samsung device. They have this device and a Samsung device. The issue on this device occurred while they were in the process of flashing their Samsung device.
I know you're trying to help but don't post anything unless you are absolutely certain that you know what you're talking about.
In this case, you didn't and that can easily lead to a hard bricked device because they followed your instruction.
Stick to answering questions about devices you personally have dealt with, don't go assuming that you understand someone else's device. They are all different, the methods, tricks and tools for one won't necessarily work on another.
You understand android somewhat but judging by your posts, you don't understand the differences in devices and methods. But you will after you've been here a while.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 10:39 PM ---------- Previous post was at 10:32 PM ----------
DO NOT USE ODIN ON YOUR DEVICE!!!
Odin is only for Samsung devices.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a device exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
thankyou so much for the fast responses much appreciated to take your time to explain. Okay i have a question what would be the course of detailed action to preform getting any and all missing .img's it may need. Also i know its a crazy question but would i be able to preform this in store with the displayed tablet that matches mine? How difficult is something like this, and is there any other methods at all I can try to boot past this bootloader. And now that i remember correctly from reading others this happened when I upgraded to 5.1 or 5.0 thank you everybody once again!
samson716 said:
thankyou so much for the fast responses much appreciated to take your time to explain. Okay i have a question what would be the course of detailed action to preform getting any and all missing .img's it may need. Also i know its a crazy question but would i be able to preform this in store with the displayed tablet that matches mine? How difficult is something like this, and is there any other methods at all I can try to boot past this bootloader. And now that i remember correctly from reading others this happened when I upgraded to 5.1 or 5.0 thank you everybody once again!
Click to expand...
Click to collapse
No, you wouldn't be able to get it from a tablet in the store, it's a rather involved process that requires connecting the device to PC, it also requires rooting the device and flashing a custom recovery, and that's all before you actually get to where you can pull the files. It'll take a couple of hours,or more to do it.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
No, you wouldn't be able to get it from a tablet in the store, it's a rather involved process that requires connecting the device to PC, it also requires rooting the device and flashing a custom recovery, and that's all before you actually get to where you can pull the files. It'll take a couple of hours,or more to do it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Is there absolutely anything i can try, just a long shot in the dark?
samson716 said:
Is there absolutely anything i can try, just a long shot in the dark?
Click to expand...
Click to collapse
The only other option is pretty risky. You can try a firmware from another device that has the same CPU and hardware as your device, you'd have to compare specs. It would have to have the same CPU, same screen resolution, same camera(front and rear), same amount of RAM, same amount of internal storage, same accelerometers, etc.. It has to have all the same components that yours has.
Sent from my SM-S903VL using Tapatalk