Hello,
I really need your help and expertise.
I got the notification that I needed to update my N7 with the latest OTA security updates. I let it do its thing and noticed after some time that it was stuck on the Google logo. I tried restarting but nothing would work. I read what I could about some people tapping the back of their units and then working again but that unfortunately didn't work for me. I tried to start in recovery mode but that didn't work and then the power plus vol up. It tried to finish installing the update. But I soon got an error message with the Android guy laying on its back with a red arrow on its stomach saying only "Error" nothing more or less. Not sure what to do next, I tried to find info on suggestions but after about 5 minutes, it seemed to try to reboot and went right back to getting stuck on the Google logo.
I've never had any issues with this. It's stock (no root) and had the Marshmallow update on it running just fine. It's completely unusable now and I have no idea what to do to try to fix this. Any suggestions would be really helpful. Thanks so much!
Please post the output of:
fastboot format cache
but if the response is "FAILED (command write failed)" then let's discuss it in the thread linked in my signature.
use nrt, would solve your problem.
---------- Post added at 03:53 PM ---------- Previous post was at 03:52 PM ----------
download the stock firmware latest and flash it either on fastboot or use nrt instead.
Related
my LG G PAD v500 is stuck at :
Fastboot mode started
udc_start()
the only thing hat i can do is to be turned off....help!!!!!!!!!!!!!!
:crying:
im unable to go to download mode...... can you please instruct me in detailed in what to do?
Hey i have the same problem
I have the same problem after i did a factory software upgrade and i was rooted but no recovery. did yo ever get it fixed
Solematrix said:
I have the same problem after i did a factory software upgrade and i was rooted but no recovery. did yo ever get it fixed
Click to expand...
Click to collapse
If this error shows up because of bad recovery, boot into normal ROM, root and flash stock recovery or twrp
If this error shows up because of bad boot.IMG, then you'll have to restore firmware from kdz file via download mode.(download mode = plug in usb plus volume up(?)... You should see a "Download" logo, brightness mat be very low and you have to squint )
Thanks
Yes thanx i figured it out from reading threw the forums but your help was much appreciated now to find out why my vk810 will not upgrade to 4.4.2 keep getting a error message
paperWastage said:
If this error shows up because of bad recovery, boot into normal ROM, root and flash stock recovery or twrp
If this error shows up because of bad boot.IMG, then you'll have to restore firmware from kdz file via download mode.(download mode = plug in usb plus volume up(?)... You should see a "Download" logo, brightness mat be very low and you have to squint )
Click to expand...
Click to collapse
Solematrix said:
Yes thanx i figured it out from reading threw the forums but your help was much appreciated now to find out why my vk810 will not upgrade to 4.4.2 keep getting a error message
Click to expand...
Click to collapse
I went to the Verizon store just now, their vk810 were still on 4.4.2, "check for update" says no update
Try updating via WiFi. If you removed any system apps, you need to put them back
Also, at least post the error :/... How can I help you debug if you don't tell me which step had the problem (can't search for update, update failed with x error code, tablet blew up to pieces during update...)
i did post it in another thread i started but never really got answers
paperWastage said:
I went to the Verizon store just now, their vk810 were still on 4.4.2, "check for update" says no update
Try updating via WiFi. If you removed any system apps, you need to put them back
Also, at least post the error :/... How can I help you debug if you don't tell me which step had the problem (can't search for update, update failed with x error code, tablet blew up to pieces during update...)
Click to expand...
Click to collapse
---------- Post added at 10:40 PM ---------- Previous post was at 10:37 PM ----------
i wiped it clean and started from new and it still say the same thing i tried it on wifi same time. i even took out my t mobile sim thinking it was that
paperWastage said:
I went to the Verizon store just now, their vk810 were still on 4.4.2, "check for update" says no update
Try updating via WiFi. If you removed any system apps, you need to put them back
Also, at least post the error :/... How can I help you debug if you don't tell me which step had the problem (can't search for update, update failed with x error code, tablet blew up to pieces during update...)
Click to expand...
Click to collapse
Hi,
Just to know if this problem is solved...
If it is, then this is most probably useless... unless somebody else stumps into the same problem.
If I can guess it correctly, this message typically display when you have rooted your V500, installed a custom recovery from an app flasher (i.e. Flashify, ROMToolBox...) and the recovery isn't compatible with your device and you tried a hard reset.
This means that you are able to boot into fastboot and that is what's going to save you
Why ? Simply put : because you can flash some files using the fastboot command line
Try to flash bootloaders, aboot, boot and recovery just for a try. You can find those I guess.
Regards.
Stuck with "Fastboot mode started"
I was currently on Altev vk81035b-rooted-SU installed but no custom recovery. I followed Altev-Hnk1 instructions for flashing aboot.4.2.2 & commands (dd if=/......Etc) you know the rest) which successfully copied the file. Then when I typed "reboot recovery" BAM, that's when my gPad slapped me in the face with the following--> Fastboot mode started udc_start()
I press & constantly hold "power & down" buttons which always brings me to "System Recovery" screen listing 4 options, "Continue reboot"-"Factory data reset"-"Wipe Cache"-"Safe mode boot". Anytime I have a problem I'll choose "safemode" which always got me back in after any "Boot Verification Errors", but now it doesn't & I'm stuck no matter what I chose. I'm starting to think I may need to connect my laptop and flash the KDZ starting from scratch with plain-Jane Verizon stock!?!? Whatcha think, yes-no-maybe so!?!? LOL
Am unlocked, S-off, rooted, otherwise stock 4.4.3. Was trying to update to the latest 4.4.4 so replaced TWRP with stock recovery. First attempt failed, red triangle. I figured this was due to Viper4android and the buildprop tweaks that required so I uninstalled the driver and replaced the buildprop with stock version. At this point, I had turned fastboot on and USB debugging off.
After this the phone will not reboot to OS. I can get the HTC screen to flash for a few seconds by pressing Power+VolUp, which then goes black and nothing happens. I can also sometimes get to bootloader, but cannot get my PC to recognize the phone in ADB so not much luck there.
I assume something went wrong with Viper4Android uninstallation or I screwed up the buildprop replacement. Am out of ideas, should I do a factory reset in the bootloader? I do have a TWRP backup, but I can't replace the recovery or anything else through ADB for that matter.
Edit: I did notice in bootloader that OS gets no version info, so something obviously gone wrong there. I just have no idea what to do without ADB. I guess I'm screwed.
Thanks for any help!
MrDelicious said:
Am unlocked, S-off, rooted, otherwise stock 4.4.3. Was trying to update to the latest 4.4.4 so replaced TWRP with stock recovery. First attempt failed, red triangle. I figured this was due to Viper4android and the buildprop tweaks that required so I uninstalled the driver and replaced the buildprop with stock version. At this point, I had turned fastboot on and USB debugging off.
After this the phone will not reboot to OS. I can get the HTC screen to flash for a few seconds by pressing Power+VolUp, which then goes black and nothing happens. I can also sometimes get to bootloader, but cannot get my PC to recognize the phone in ADB so not much luck there.
I assume something went wrong with Viper4Android uninstallation or I screwed up the buildprop replacement. Am out of ideas, should I do a factory reset in the bootloader? I do have a TWRP backup, but I can't replace the recovery or anything else through ADB for that matter.
Edit: I did notice in bootloader that OS gets no version info, so something obviously gone wrong there. I just have no idea what to do without ADB. I guess I'm screwed.
Thanks for any help!
Click to expand...
Click to collapse
Go to captain throbacks site for our m8 he has twrp fishable zips that you flash in your bootlloader. After that you can do a restore or reflash whatever. It might not show the proper os in bootlloader but don't worry bout it you can fix after. You'll be able to see what one your on after you get up and running again. Hopefully that should work. Just make sure you follow the directions correctly on his site. Just Google captain throwback.
---------- Post added at 02:02 AM ---------- Previous post was at 01:57 AM ----------
str8str said:
Go to captain throbacks site for our m8 he has twrp fishable zips that you flash in your bootlloader. After that you can do a restore or reflash whatever. It might not show the proper os in bootlloader but don't worry bout it you can fix after. You'll be able to see what one your on after you get up and running again. Hopefully that should work. Just make sure you follow the directions correctly on his site. Just Google captain throwback.
Click to expand...
Click to collapse
Also best way to update your firmware is thru a bootlloader flushable zip as well you don't have to worry about restoring stock recovery and doesn't matter what rom your on etc. There are threads on how to do it very easy.
str8str said:
Go to captain throbacks site for our m8 he has twrp fishable zips that you flash in your bootlloader. After that you can do a restore or reflash whatever. It might not show the proper os in bootlloader but don't worry bout it you can fix after. You'll be able to see what one your on after you get up and running again. Hopefully that should work. Just make sure you follow the directions correctly on his site. Just Google captain throwback.
---------- Post added at 02:02 AM ---------- Previous post was at 01:57 AM ----------
Also best way to update your firmware is thru a bootlloader flushable zip as well you don't have to worry about restoring stock recovery and doesn't matter what rom your on etc. There are threads on how to do it very easy.
Click to expand...
Click to collapse
Thanks! I shall look into this.
Hello,
I am not new to rooting, made a mistake in installing cyanogemod 10.2.1 on my S3. I had the Status 6 error, saw some troubleshoot fix online and it told me to delete the first line from the Update Script inside the google folder. I went to recovery, installed the rom, it said restart, so i did. Now my S3 wont load into recovery or to download mode at all. Although i still see the qhsusb_dload in device manager when i plug it in my pc.
I have tried booting from an sd card but i got nothing, i kept on trying different debrick images from everywhere and i dont know if i have the right one. My phone was in 4.4.2 before all this happened. Please help because i just got this new phone and i really dont have money to jtag. My parents would kill me.
Thank you.
http://forum.xda-developers.com/showthread.php?t=2549068
---------- Post added at 12:00 PM ---------- Previous post was at 11:52 AM ----------
http://forum.xda-developers.com/showthread.php?t=2962626
Hi,
I know this is a typical newbie has no idea what he's doing scenario, so I apologize. However, I feel like I've tried everything and am yielding no results.
I am trying to root a Verizon LG G3. Since I'm not entirely sure as to the technical details, I want to explain what I think I know. To my understanding, there are different versions of VS985? I haven't seen anything resembling 49A, 49B, or 49C, but the closest thing I found was the software version which said VS9854CA.
The first thing I tried was the One Click Root tool. The tool did not find any methods of rooting though. The next thing I tried was TowelRoot. I set my phone to stay awake while charging, and pressed the "Make it rain" button. It turned yellow as a response, but did not do anything else even after leaving the phone untouched for eight hours. I also tried to ADB tools but "adb reboot fastboot" only rebooted the phone back into the OS, and "adb reboot recovery" showed an android figure with the words "No Command" for a small duration before rebooting back into the OS. The final guide I tried was the KDZ and TOT methods. KDZ resulted in the message "Upgrade stopped due to an error," and TOT displayed "READY!" for the COM41 but did not attempt anything even after unplugging and plugging the phone back in.
Can anyone help me please? Could there be something I'm doing wrong in any of those methods?
I appreciate all the help I get. Thank you.
I'm in the same boat. I just got this phone from eBay, thought it would be easy to root as I used to have one and that was my experience at that time. Things have changed... There is no root for this latest software version 4CA. Totally sucks!
Any suggestions for a comparable phone that can be rooted when on the latest stock update? I'm on Verizon btw...
just use the LGFlash Tool 2014 and flash the 47A KDZ (6.0) file and then rooted using KingRoot 4.9.6 .. Now going to flash twrp and them fulmics rom.
I have tried everything else nothing worked for me. I was on VS985.... MRA58K (6.0.1).. Tot method didn't worked...flashing 10b KDZ also didn't worked.. They keep giving error.
---------- Post added at 04:33 PM ---------- Previous post was at 03:44 PM ----------
Twrp flash doesn't worked and i lost my stock recovery too. NOw just flash 10B Tot with 35B dll and m back to Kitkat. Hope so everything will work now
---------- Post added at 04:55 PM ---------- Previous post was at 04:33 PM ----------
got the red factory reset with status 2.. I had to flash kdz 24b now my phone is booting
Need some guidance on this one. Went through trying to root my Note 4. Upgraded from 4.4.4 to 5.1.1 after all this time waiting. From there, continually hitting soft bricks (referring to endless boot loop in regards to soft brick) and a lot of the issue I believe to be my battery. However, was originally able to flash the 5.1.1 FW (N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar.md5) and the brick would be remedied. At this point however, the note just goes into a endless boot loop where only thing it displays is the "Samsung Galaxy Note 4 Powered by Android" splashscreen (Never displays the oval samsung or verizon splashscreens) and vibrates twice as the screen display goes off for about 3 secs and pops back up with the same screen over again. At this point, the only thing I have found to remedy this is the Verizon Software Update program, which instantly updates to 6.0.1 (newest FW). This wouldn't be an issue, with the exception that the 5.1.1 FW still puts the phone into the soft brick state. Anyone have an idea why the FW is now putting into a brick and how to fix the issue so I can downgrade successfully?
In case it matters, to get the Verizon program to work, I would flash "N910VVRU2BPA1_StockRestore.tar.md5" via Odin and from there, download mode would then populate a screen stating update failed and to utilize the program. Seems to be the only way to get it to be able to connect.
Also, with all that said, the one thing I have thought about doing, but haven't is re-partitioning with a PIT file. However, I have not come across any threads on re-partitioning the Note 4 and those that refer state not to. With that said, I wouldn't mind attempting it if someone else feels like it may work. If so, please lead me to a thread with instructions along with a correct PIT file in order to run through the process please.
hey man I'm actually running into a similar issue. Ran into it while attempting to Root via Kingroot on 5.0.1 I was following a guide, the phone rebooted on it's own during the process and didn't have any issues rebooting, but at one point I wanted to reboot and instead of pulling the battery like normal, I decided to press the reboot option in the power menu, bad idea, now I'm bricked and Odining PA1 is not allowing a proper boot... have you found a solution to your problem? maybe it would help me with mine
---------- Post added at 10:52 PM ---------- Previous post was at 10:50 PM ----------
well after a really long battery pull, its booting up for me, I hope you were able to resolve this issue