Related
I have read many times over now jcase method and have tried it twice now without success- clearly I am doing something wrong. I have working adb on my pc and all the prerequisite files in the correct directory. I seem to be going wrong at the "adb restore backup.ab" point- it says allow it to restore but in my terminal that process is very quick and the phone does nothing. Am I not waiting long enough?...and appears as if nothing else happens so I go to first terminal and stop it as directions say...but after that the next important 5 code steps say failed or file not found-is that what is supposed to happen?...I finish the remaining steps and then head to htc un unlock but it comes back FAILED Anyone with success have any tips?? I'm stumped...but not bricked...yet!
are you connected to the internet during that time ?
Allowing it to restore means to acknowledge it on the phone itself. Touch the appropriate button on the phone.
Sent from my HTC6435LVW using xda premium
Unlock your phone and click the allow button.
Sent from my GT-P7510 using xda app-developers app
And after touching the "allow" button,, be prepared to wait several minutes. That command is restoring a 300 mob for. It takes awhile.
Sent from my Nexus 7 using Tapatalk 2
more Q's
Appreciate the help guys! So I should see a message on my phone that requires me to allow? That I did not see or do...sounds hopefull. I have been thinking my adb version was not supporting restore as when I did the restore step all I see is like a help screen, with no direction to allow, or continue or yes/no.....and yes I was connected to internet...should I not be? Won't be able to try this again till tonight but really appreciate the help!
After using the adb restore command, you should turn your phone screen on, and there should be a message waiting that is asking you to confirm that you want to restore.
If you aren't seeing that message after turning your phone screen on, then it sounds like your adb might be too old, our you got a bad download of backup.ab
Sent from my HTC6435LVW using Tapatalk 2
rootntootn said:
Appreciate the help guys! So I should see a message on my phone that requires me to allow? That I did not see or do...sounds hopefull. I have been thinking my adb version was not supporting restore as when I did the restore step all I see is like a help screen, with no direction to allow, or continue or yes/no.....and yes I was connected to internet...should I not be? Won't be able to try this again till tonight but really appreciate the help!
Click to expand...
Click to collapse
I made this mistake last night
is the backup.ab file in the same folder as the adb command is?
I forgot to move the backup file and that is when you get the help screen..
munchy_cool said:
I made this mistake last night
is the backup.ab file in the same folder as the adb command is?
I forgot to move the backup file and that is when you get the help screen..
Click to expand...
Click to collapse
Will check all this stuff out, all sounds like it's pointing me in the right direction and I am a bit complsive so I will get there sooner or later, any other thoughts will be greatly appreciated and investigated...I think my files are where they are supposed to be BUT I will check and re-check
try it and let us know dude ..do not proceed until you are sure backup is done
Ok...some success, did it in win 8 but I think it was my version of adb that was the problem..not version of windows or files-however I had a zillion files and shortcuts on 7 and I was getting confused so I switched.
I did now get the backup to run, unlocked and allowed on phone...let it finish and all seemed great but last step before reboot...the "adb shell dd if=/sdcard/CIDBLOCK.img of=/dev/block/mmcblk0p5" code returned something like permission denied? Anyway I did reboot and did try for the hell of it, to unlock at HTC...but of course It FAILED. I did not factory reset this time so I am thinking maybe that's the problem and will try again later. Any other thoughts on this demise?
Maybe windows 8 is the problem
droid DNA \m/ √[π]¶~™
munchy_cool said:
Maybe windows 8 is the problem
droid DNA \m/ √[π]¶~™
Click to expand...
Click to collapse
Could be except that it did work up to that (almost) last step...I did read to factory reboot before trying again but I did not...mostly because I was lazy...but also because the image files were already in my phone storage anyway and that,s what the first few steps do...I started from backup.ab code part so I will do the whole deal over...later-burned at the moment.
Done Deal
rootntootn said:
Could be except that it did work up to that (almost) last step...I did read to factory reboot before trying again but I did not...mostly because I was lazy...but also because the image files were already in my phone storage anyway and that,s what the first few steps do...I started from backup.ab code part so I will do the whole deal over...later-burned at the moment.
Click to expand...
Click to collapse
Well...It all finally went well!! Can't thank members enough for all the help...I will pay it forward!!
Hi all, unfortunately, i have bricked my phone, and it now can't turn on..
I have a backup of the software(My friend gived me it), but when i put it in SP Flash Tool, i see only the red bar, then the program don't flash anything..
My computer see the phone as "MTK USB Port (COM6)"..
Is this the problem maybe?
Please help me..
Sorry for my bad english, I'm italian..
#UP
No one can help me please?
Did you use MTK droid tools to make a backup? I know you may have done this all ready, but did you download the drivers and checked in device manager on your computer to see if you can see the phone? Sometimes if you remove the battery, and connect it to the computer. (with a good USB lead ) it should install the phones drivers. Did you also install adb on your computer? As if you did, you should be able to get into recovery. By typing adb reboot recovery and it should boot into c.w.m. recovery. Hope this helps. I'm still getting used to mine. Sorry I can't help with more advice, hopefully someone on here can help.
Sent from my I9389 using xda app-developers app
hey everyone i need your help unbricking my haipai too, i deleted some system apps now its restarting (bootloop in android loading screen, sometimes launcher appears for some seconds and bootloop again) and i think its because of the s4 water apk - can somebody pls upload this apk or better all system apks from i9389 ? cant extract the system.img from needrom... and i didnt have a special cable to flash via sp tool. i got this phone yesterday it was great as i say i deleted some and after reboot all fun is gone ;P
Hi. I just did the same thing. Got rid of s4 wate r and now continual boot loop. I cant get into titainium to get it back.
Sent from my GT-P5110 using Tapatalk 2
Hi. Can anyone help with this topic. I have rooted my i9389. Backed it up with titanium. The whilst removing some bloat whare have sent my phone into a boot loop. I have no pc just a tablet. And when I did manage to connect to a pc it would not recognize the phone. When I turn it on and try to open back up or titanium or anything else for that matter it loops before I can get anywhere. Please help.
Sent from my GT-P5110 using Tapatalk 2
Mine died ...getting no network and signal and I know its not my sim card.quite a few have died this way.
Sent from my Blade using xda app-developers app
Hey guys. I was going to post this on the Android Forums, but the L9 board there isn't getting hardly any traffic, so I suppose I'll just repaste here:
Hey guys, it's loopy time. xD
I've been through XDA, again, nobody seems to really have an answer for this, or even an answer for me. There's this guy over there named Kuma that made a stock 2nd-init locked bootloader ROM based off of 10e. I don't really desire to go back to it, but I like the fact that it comes with the xposed framework which you all know is an easy way to theme things that you should be able to theme, like making the status bar and notification area transparent.
I made a mistake in thinking that you can install Chainfire 3D on a locked BL, boy was I wrong. Two soft bricks later, I end up on 10d then do the OTA update to 10e. I've got the LG Mobile Support tool working as the offline flash. So I threw d on there and it worked....until I decided that I wanted to enable USB debugging.
There was a thread where I was advised to use Fastboot to flash the U and X boots, which I succeeded, but it wiped most of the partitions. At first I was panicking like...OMG, the family is going to worry because at this point I thought I was hard bricked, and my father is ill yada yada. So after about twenty minutes of crying and flipping out, I was able to get the USB for fastboot working with OMAP (which is tricky to install!) Three bottles of Pepsi Cola later, some chips, and a honey bun, I was able to get back to stock 10d.
Now, I've tried various drivers to try and get this thing to a go for ADB so I could root, install 2nd-init, and get Kuma's ROM back. I tried the updated drivers from the LG website. I have tried LG drivers 3.8.1.
The issue that I am having is that I am unable to access any of the connectivity modes while USB debugging is checked. If I uncheck it and try to plug it in, everything works perfectly. However, when USB Debugging is checked, no matter what connectivity mode I am on, I suffer with the LG Software coming up in autoplay and furthermore disconnecting after about ten seconds.
I tried in Ubuntu Linux to get it to work, and the same thing happens. This leads me to believe that either there is something wrong with the phone or something wrong with my computer, but other devices work. I'm really confused. Is there partitions for 10e MS769 MetroPCS that I can flash via fastboot to correct this? Is there another tool I can use to do this? I pretty much know fastboot is the key, but i'm going to need some assistance.
Hope you guys have an answer. I sure don't.
Please help me with this. I am familiar with fastboot maybe its a bad .bin file?
Assistance would be appreciated.
Thanks,
LoopyD
Bump.
Anyone?
Had the same problem, usb debug and any sort of adb connection doesn't work. Kuma comes to the rescue like the super hero he is and helped me fix it. Here is the post http://forum.xda-developers.com/showthread.php?p=49475336#post49475336 . Oddly enough this problem got worse for me I had it for about 3 months and it resulted in constant crashes and constant resets. Thank Kuma's post if it works!
Thank you sir. The ADB executable installer now shows the device. Problem solved.
Thanks
Sent from my LGMS769 using Tapatalk
I have searched for 6 hours last night and again for several this morning on all the forums I could.
My phone has nothing left on it except recover. I have TWRP loaded, don't know how, but nothing in any folders.
I was trying to start from scratch with my phone and just wiped everything so I could reload and start over.
Stupid idea I know!
I can get my PC to recognize the phone. I am using Windows 7 and in cmd prompt I can find the phone but I do not know how to sideload or anything like that. I tried following a couple forums on it but no success.
please help
a huge thanks in advance
Minahan1 said:
I have searched for 6 hours last night and again for several this morning on all the forums I could.
My phone has nothing left on it except recover. I have TWRP loaded, don't know how, but nothing in any folders.
I was trying to start from scratch with my phone and just wiped everything so I could reload and start over.
Stupid idea I know!
I can get my PC to recognize the phone. I am using Windows 7 and in cmd prompt I can find the phone but I do not know how to sideload or anything like that. I tried following a couple forums on it but no success.
please help
a huge thanks in advance
Click to expand...
Click to collapse
I think side load is under the advanced options in TWRP, start t there and follow directions.
There is an option in recovery that will lead to this position
Minahan1 said:
I have searched for 6 hours last night and again for several this morning on all the forums I could.
My phone has nothing left on it except recover. I have TWRP loaded, don't know how, but nothing in any folders.
I was trying to start from scratch with my phone and just wiped everything so I could reload and start over.
Stupid idea I know!
I can get my PC to recognize the phone. I am using Windows 7 and in cmd prompt I can find the phone but I do not know how to sideload or anything like that. I tried following a couple forums on it but no success.
please help
a huge thanks in advance
Click to expand...
Click to collapse
In recovery click advanced then click sideload, it then will wait for you to send the ROM. Open adb and you will then enter: adb sideload C:\path\to\rom.zip
After you do that it will slowly start to send it to the device and begin the flashing process
Alternatively you can use: adb push C:\path\to\rom.zip /sdcard/rom.zip
And then just flash it normally.
I got it to work thank you
.torrented and RLGL
I was being impatient, frustrated and very pissed off for my careless actions.
After paying attention to what I was trying to do I did figure out the path I was writing was wrong.
All is well
If anyone is going to attempt or need this fix pay attention to the details.
thanks again guys
It sound pretty bad situation you are facing. Were u missed out some step when wipe it out?
Sent from my HTC6435LVW using Tapatalk
What happened was I was trying to root my kindle fire HDX with this thread. http://forum.xda-developers.com/showthread.php?t=2689121
I put in "adb reboot bootloader" and it was fine.
After, I put in "fastboot -i 0x1949 flash boot boot.img" and that's where stuff went downhill. Basically my kindle just got stuck at the kindle fire logo, where the kindle is "silver" and the "fire" is orange with the gradient of light going across it.
It was stuck on waiting for device for 10 minutes, so I shut it down by holding the power for 30 seconds and disconnected it.
Ever since then, when I restart the kindle, it just shows the kindle fire shining logo and that's it. I can't do anything else.
I'm very new to this kind of stuff, was doing this with the help of my friend, but now we're both stumped.
Any help would be really helpful. If I could factory reset, I would, so there's a lot of stuff I'm willing to do and part with the info on this kindle. I just want it to be working again.
Thank you for reading this and any help at all would be greatly appreciated!
Edit: Oh, and if it helps, I was running 14.3.2.2 instead of 14.3.2.1.
I didn't think it would make that big of a difference, but I definitely learned my lesson.
uberiyer1 said:
What happened was I was trying to root my kindle fire HDX with this thread. http://forum.xda-developers.com/showthread.php?t=2689121
I put in "adb reboot bootloader" and it was fine.
After, I put in "fastboot -i 0x1949 flash boot boot.img" and that's where stuff went downhill. Basically my kindle just got stuck at the kindle fire logo, where the kindle is "silver" and the "fire" is orange with the gradient of light going across it.
It was stuck on waiting for device for 10 minutes, so I shut it down by holding the power for 30 seconds and disconnected it.
Ever since then, when I restart the kindle, it just shows the kindle fire shining logo and that's it. I can't do anything else.
I'm very new to this kind of stuff, was doing this with the help of my friend, but now we're both stumped.
Any help would be really helpful. If I could factory reset, I would, so there's a lot of stuff I'm willing to do and part with the info on this kindle. I just want it to be working again.
Thank you for reading this and any help at all would be greatly appreciated!
Edit: Oh, and if it helps, I was running 14.3.2.2 instead of 14.3.2.1.
I didn't think it would make that big of a difference, but I definitely learned my lesson.
Click to expand...
Click to collapse
If you can reboot into the bootloader again, it might be worth it to try the same commands, but with the boot.img pulled from 14.3.2.2.
S_transform said:
... but with the boot.img pulled from 14.3.2.2.
Click to expand...
Click to collapse
I don't think this matters... if the HDX 8.9 is anything like the HDX 7, the boot.img file is identical in both the 13.3.2.1 and 13.3.2.2 versions. I did a binary-compare when 13.3.2.2 was released, and they're bit-for-bit identical. FYI.
[Edit] However, there is significant difference in the boot.img between versions 13.3.1.0 and 13.3.2.1. [/Edit]
tl3 said:
I don't think this matters... if the HDX 8.9 is anything like the HDX 7, the boot.img file is identical in both the 13.3.2.1 and 13.3.2.2 versions. I did a binary-compare when 13.3.2.2 was released, and they're bit-for-bit identical. FYI.
[Edit] However, there is significant difference in the boot.img between versions 13.3.1.0 and 13.3.2.1. [/Edit]
Click to expand...
Click to collapse
I was not aware, thanks for the heads up!
No, the root method in my thread unfortunately is non-working. I intended for boot.img to be flashed when the "fastboot" screen is showing. Unfortunately, the hdx does not go into fastboot like its sister device the HD 2013. Reading earlier posts in the thread would show you that it does not work.
But this is puzzling. Did you use a fastboot cable? If not then it was not my root method that bootlooped your device, and you should be able to get a replacement. If you DID use a factory cable, I can help you fix it.
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Mineturtle33 said:
No, the root method in my thread unfortunately is non-working. I intended for boot.img to be flashed when the "fastboot" screen is showing. Unfortunately, the hdx does not go into fastboot like its sister device the HD 2013. Reading earlier posts in the thread would show you that it does not work.
But this is puzzling. Did you use a fastboot cable? If not then it was not my root method that bootlooped your device, and you should be able to get a replacement. If you DID use a factory cable, I can help you fix it.
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Click to expand...
Click to collapse
how can you help fix with a fastboot cable??
jjrizzelcincy said:
how can you help fix with a fastboot cable??
Click to expand...
Click to collapse
Did you use a fastboot cable or not. If you didnt, it wasnot my root method that killed your device, and if you did, it still might not have been. It depends on whether the tablet's "fastboot" screen appeared when you used the cable. If so, i can help you recover it.
So...
•did you use a fastboot cable?
If yes
•did a fastboot screen pop up?
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Mineturtle33 said:
Did you use a fastboot cable or not. If you didnt, it wasnot my root method that killed your device, and if you did, it still might not have been. It depends on whether the tablet's "fastboot" screen appeared when you used the cable. If so, i can help you recover it.
So...
•did you use a fastboot cable?
If yes
•did a fastboot screen pop up?
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Click to expand...
Click to collapse
i am only asking how you might go about fixing his problem to learn something new about the device ,that is why i asked you how you would go about that with a fastboot cable your root method did not brick my device
jjrizzelcincy said:
i am only asking how you might go about fixing his problem to learn something new about the device ,that is why i asked you how you would go about that with a fastboot cable your root method did not brick my device
Click to expand...
Click to collapse
If you want me to fix it you need to answer the questions or I can't help you. I'm doing my best.
Sent from my Galaxy Nexus using Tapatalk
Mineturtle33 said:
If you want me to fix it you need to answer the questions or I can't help you. I'm doing my best.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
again i did not brick my device
using your root method
my device got bricked by an error in safestrap
i did a wipe data factory reset and this when i went to reflash the rom on the rom slot and it kept saying flash failed and that there were 0 mb on the sdcard i even pushed the rom back to the sdcard from adb but it would not flash and when i went to reboot it gave me a warning saying no os found or something like that so i tried and tried to make another rom slot and tried to restore a backup but it would not let me saying 0mb of storage available
so that's my story and now i dont have adb and im stuck at the gray kindle fire logo with only mtp showing but not fully installing but with a fastboot cable i got QHSUSB_BULK at first but after some booting over and over again i got it into QHSUSB_DLOAD with a driver installed on windows and i can see it connected to Linux as well with an id and everything in lsusb from a terminal that is about where my knowledge ends
but with the right devs we could get this working like the evo 3d and a bunch
of other HTC devices that were fixed that way and even get s-off through that QHSUSB_DLOAD mode but i dont have the knowledge to write something like that up or how to issue the proper commands in Linux or what partitions to write to or even the proper chmod to make so im stuck with a nice little paper weight as of now with no devs on board it's looking a bit grim for me
jjrizzelcincy said:
again i did not brick my device
using your root method
my device got bricked by an error in safestrap
i did a wipe data factory reset and this when i went to reflash the rom on the rom slot and it kept saying flash failed and that there were 0 mb on the sdcard i even pushed the rom back to the sdcard from adb but it would not flash and when i went to reboot it gave me a warning saying no os found or something like that so i tried and tried to make another rom slot and tried to restore a backup but it would not let me saying 0mb of storage available
so that's my story and now i dont have adb and im stuck at the gray kindle fire logo with only mtp showing but not fully installing but with a fastboot cable i got QHSUSB_BULK at first but after some booting over and over again i got it into QHSUSB_DLOAD with a driver installed on windows and i can see it connected to Linux as well with an id and everything in lsusb from a terminal that is about where my knowledge ends
but with the right devs we could get this working like the evo 3d and a bunch
of other HTC devices that were fixed that way and even get s-off through that QHSUSB_DLOAD mode but i dont have the knowledge to write something like that up or how to issue the proper commands in Linux or what partitions to write to or even the proper chmod to make so im stuck with a nice little paper weight as of now with no devs on board it's looking a bit grim for me
Click to expand...
Click to collapse
Oh my god I'm an idiot. I thought you were the op. *facepalm* sorry for the trouble.
Sent from my Galaxy Nexus using Tapatalk
Mineturtle33 said:
Oh my god I'm an idiot. I thought you were the op. *facepalm* sorry. For the trouble.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
NOPE you are stuck helping me now lol
jjrizzelcincy said:
NOPE you are stuck helping me now lol
Click to expand...
Click to collapse
I'll look into it. But as of now I'm a bit busy. Sorry.
Sent from my Galaxy Nexus using Tapatalk
Mineturtle33 said:
I'll look into it. But as of now I'm a bit busy. Sorry.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
the only way i see a fix for mine since the fastboot cable did not help me get into fastboot mode is if we some how manage to get some devs over here which seems unlikely at this point but i still have hope one falls on a devs lap sometime soon