This will help you unbrick a bricked FireTV 2. You must download the following:
FireTV 2 Recovery Installer
FireTV 2 Recovery
Unbrick Images (md5sum: 5e774497b3bad5c47d1c744410f6db12)
Extract all 3 zip files to the same directory.
You must decide if you want to use unbrick.img or unbrick+ramdisk.img. Using unbrick.img, it should take about 30 minutes. Using unbrick+ramdisk.img it could take up to 2 hours. You can only use unbrick.img if you have an sdcard. If you have an sdcard, place ramdisk-recovery.cpio.lzma in the root directory of it.
Run unbrick_firetv2.bat for Windows or unbrick_firetv2.sh for Linux or OSX.
First, it will ask you which file you want to use, unbrick.img or unbrick+ramdisk.img. You must type the name of the image you want to use.
Make sure the USB cable is connected and turn on the FireTV 2.
Then it will start reading from the FireTV. Then it will prompt you with a warning:
Code:
No target file specified. Is this a partition image?
If this is not, DO NOT CONTINUE, otherwise press 'y' to continue.
Write partition image? <y|n>
Type a 'y' and hit enter.
It should start writing. Eventually it will finish. If you put the ramdisk on the sdcard, make sure it is plugged in and power cycle the Fire TV. It should skip the bootmenu and take you straight to recovery. If for some reason the USB keyboard doesn't work, unplug and replug it. It should start working.
rbox said:
This will help you unbrick a bricked FireTV 2. You must download the following:
FireTV 2 Recovery Installer
FireTV 2 Recovery
Unbrick Images
Extract all 3 zip files to the same directory.
You must decide if you want to use unbrick.img or unbrick+recovery.img. Using unbrick.img, it should take about 30 minutes. Using unbrick+recovery.img it could take up to 2 hours. You can only use unbrick.img if you have an sdcard. If you have an sdcard, place ramdisk-recovery.cpio.lzma in the root directory of it.
Run unbrick_firetv2.bat for Windows or unbrick_firetv2.sh for Linux or OSX.
First, it will ask you which file you want to use, unbrick.img or unbrick+recovery.img. You must type the name of the image you want to use.
Make sure the USB cable is connected and turn on the FireTV 2.
Then it will start reading from the FireTV. Then it will prompt you with a warning:
Code:
No target file specified. Is this a partition image?
If this is not, DO NOT CONTINUE, otherwise press 'y' to continue.
Write partition image? <y|n>
Type a 'y' and hit enter.
It should start writing. Eventually it will finish. If you put the ramdisk on the sdcard, make sure it is plugged in and power cycle the Fire TV. It should skip the bootmenu and take you straight to recovery. If for some reason the USB keyboard doesn't work, unplug and replug it. It should start working.
Click to expand...
Click to collapse
Awesome rbox! I see you've been busy...Really appreciate everything you do for us Fire TV folks.
Awesome work as always!
Thank you mate... Your great work made my day and got out of bricked state !!!!!
Got to recovery and flashed your rooted 5.0.31 and rebooted to perfectly working aftv2 + rooted .. Good job as always mate , thanks
One question, could I just flash the rooted 5.0.4 from recovery or should I do something else??
samykoka said:
Thank you mate... Your great work made my day and got out of bricked state !!!!!
Got to recovery and flashed your rooted 5.0.31 and rebooted to perfectly working aftv2 + rooted .. Good job as always mate , thanks
One question, could I just flash the rooted 5.0.4 from recovery or should I do something else??
Click to expand...
Click to collapse
You can flash whatever version you want...
rbox, looks like amazon sent me a bricked fire tv, while im at possession, i figured a i play around with it.
when i got it it was stuck to amazon white amazon logo,
so i waited for it for like 30 minutes to boot, but nothing changes... then with recent root method (aftv gen 2)
i figured i install this
http://forum.xda-developers.com/fire-tv/development/firetv-2-recovery-t3309780/page17#post65265240
i was able get to recovery!
and applied pre rooted firmware, but after completion,
i think its beyond bricked..
no screen, my led flash drive does not even flash or blink anymore when i put it on boot...
i can still handshake still apply the unbrick method
my question is after applying this brick.img
would i suppose to get a screen? and boot up
but still the same no screen nothing... not even white amazon logo...
or this is done..
thanks
daffung said:
rbox, looks like amazon sent me a bricked fire tv, while im at possession, i figured a i play around with it.
when i got it it was stuck to amazon white amazon logo,
so i waited for it for like 30 minutes to boot, but nothing changes... then with recent root method (aftv gen 2)
i figured i install this
http://forum.xda-developers.com/fire-tv/development/firetv-2-recovery-t3309780/page17#post65265240
i was able get to recovery!
and applied pre rooted firmware, but after completion,
i think its beyond bricked..
no screen, my led flash drive does not even flash or blink anymore when i put it on boot...
i can still handshake still apply the unbrick method
my question is after applying this brick.img
would i suppose to get a screen? and boot up
but still the same no screen nothing... not even white amazon logo...
or this is done..
thanks
Click to expand...
Click to collapse
After using unbrick.img, if you put the ramdisk on the sdcard, you should get recovery. If not, then there is something bad the hardware.
Many thanks, rbox -- unbrick_firetv2.bat worked for me in bootcamp. Selected unbrick+ramdisk.img, then rebooted into TWRP. Initially when I installed prerooted 5.0.5_r2, setup gave me a screen (after remote pairing and language selection) that it was checking for updates. The setup then halted with an error window that it could not connect to Amazon's server, and that I should power off and reset the AFTV. I then flashed prerooted 5.0.4_r2, completed the initial setup, and reflashed prerooted 5.0.5_r2 (which let me get around the update error).
Again, thanks for all your work!!
rbox said:
After using unbrick.img, if you put the ramdisk on the sdcard, you should get recovery. If not, then there is something bad the hardware.
Click to expand...
Click to collapse
i wonder what caused that bricked.. , ( well it was already bricked, when amazon send it to me it was stuck at white amazon logo, then only when i applied the pre rooted firmware, thats when it stop showing screens from there..wouldn't it fix the problem already since i was able to get to recovery.....
id try the sd card 1 last thing il probably go to walmart and try that, if nothing fix it i guess its total beyond brick..
Hi,
thank you very much for your great work @rbox!
Just a note:
I think, in the bash script, there is a "2" in the last line that doesn't belong there?
And there is a "unbrick+ramdisk.img" file, but no "unbrick+recovery.img" in the zip container. Some might get confused by that...
But everything works fine (using ramdisk)!
thx
Takeoo111111 said:
Hi,
thank you very much for your great work @rbox!
Just a note:
I think, in the bash script, there is a "2" in the last line that doesn't belong there?
And there is a "unbrick+ramdisk.img" file, but no "unbrick+recovery.img" in the zip container. Some might get confused by that...
But everything works fine (using ramdisk)!
thx
Click to expand...
Click to collapse
Thanks. I fixed it all.
rbox said:
After using unbrick.img, if you put the ramdisk on the sdcard, you should get recovery. If not, then there is something bad the hardware.
Click to expand...
Click to collapse
rbox, looks like its a hardware problem? but problem is i had white screen when i applied the pre rooted fire tv, thats when i get no screen, no boot... do think its possible a fix for this, via handshake?
daffung said:
rbox, looks like its a hardware problem? but problem is i had white screen when i applied the pre rooted fire tv, thats when i get no screen, no boot... do think its possible a fix for this, via handshake?
Click to expand...
Click to collapse
Well try the unbrick image and see if it works.
rbox said:
After using unbrick.img, if you put the ramdisk on the sdcard, you should get recovery. If not, then there is something bad the hardware.
Click to expand...
Click to collapse
rbox said:
Well try the unbrick image and see if it works.
Click to expand...
Click to collapse
yup,
sucessfully flashed unbrick.img, and had sd card ramdisk-recovery.cpio.lzm.
still the same...
no boot, no screen, not even white screen?
and no signal from hdmi
I am afraid I have to report a brick on 5.0.5r3 -
Played some Vice City, went back into Kodi, played a video that was still in the paused state, then the screen flashed to black and then back to the Video in Kodi twice and then - a dreaded blackscreen.
Upon a reboot I still get the amazon logo, I get the recovery bootscreen and also can still enter TWRP recovery, but when I try to boot into the normal OS I only get the amazon logo and then a fade to black (amazon Fire TV animated logo not showing up). The blue LED on the Fire TV is steadily blinking along...
(Switched TVs and HDMI cables - just in case (no HDCP problem.. ))
Already wiped /system /data /data including media /cache and /dalvik - and reinstalled both 5.0.5r1 and r3 multiple times.
Right now I have two questions - 1st (for the fast ones, because I am trying it anyway) - should I still try to unbrick using this tutorial (i.e. If I have access to the recovery and already formated the whole range of partitions once - does the unbrick image do anything more than that?).
And 2nd - is there any "factory image" maybe without the stock recovery disabled - just in case, at this point - I'd try most things - really...
harlekinrains said:
I am afraid I have to report a brick on 5.0.5r3 -
Played some Vice City, went back into Kodi, played a video that was still in the paused state, then the screen flashed to black twice and then - a dreaded blackscreen.
Upon a reboot I still get the amazon logo, I get the recovery bootscreen and also can still enter TWRP recovery, but when I try to boot into the normal OS I only get the amazon logo and then a fade to black (amazon Fire TV animated logo not showing up). The blue LED on the Fire TV is steadily blinking along...
(Switched TVs and HDMI cables - just in case (no HDCP problem.. ))
Already wiped /system /data /data including media /cache and /dalvik - and reinstalled both 5.0.5r1 and r3 multiple times.
Right now I have two questions - 1st (for the fast ones, because I am trying it anyway) - should I still try to unbrick using this tutorial (i.e. If I have access to the recovery and already formated the whole range of partitions once - does the unbrick image do anything more than that?).
And 2nd - is there any "factory image" maybe without the stock recovery disabled - just in case, at this point - I'd try most things - really...
Click to expand...
Click to collapse
The unbrick image just puts enough on system to be able to get to recovery. If you can already get to recovery, it won't get you anything. The disabled stock recovery isn't going to effect anything while running android. All it does it prevent the bootloader from running it. I can't really explain it if you did an advanced wipe of data.
Hardware Issue probably. Thanks for the fast response.
Cheers.
(I'll do another advanced wipe - just for kicks.. )
edit: Went through with another full wipe - rebooting the device afterwards (= softbrick for sure, because not even TWRP is accessible and there is no OS on the device) - which at that point got "parked" on the white amazon logo indefinitely. (Perfect for the "I aint know nothing" returning the device approach. Just in case Amazons 5.0.5 turns out to brick a few more Fire TVs... As long as rbox didnt modify the kernel, I'd say its Amazons fault. ) Then went through the unbrick procedure in this thread - which worked as described (TWRP was installed on the device and autobooted on the powercycle after the unbrick script had finished). Then installed 5.0.5r1 again and rebootet - just to be met with the same error profile as before "dark screen" - not even the animated amazon logo (just the white one in the beginning).
This time - on a better TV screen it was visible though, that the screen showed a small horizontal line, and then flashed in a lighter black color twice, before going back to full TV black. So yes the problem seems to lay somewhere on the video signal path. Its curious though, that TWRP still got (and gets) displayed...
Works perfect. Thx
Can someone help me? I followed all the steps in the guide and when the unbricking program is writing the filesystem, it always gets stuck at 17%. Maybe I am doing something wrong?
rbox said:
After using unbrick.img, if you put the ramdisk on the sdcard, you should get recovery. If not, then there is something bad the hardware.
Click to expand...
Click to collapse
I am in a boot loop. Goes to amazon white logo. Light on FireTV2 turns orange then reboots into custom recovery but it automatically starts trying to mount partitions (one of them is cache) and it fails on all of them. Then moves along to the white amazon screen again and repeats the entire process. I ran the unbrick.img and the problem persists.
I'm currently in the process of running unbrick+recovery.img method to see if it makes any difference. Should it? Is there anything that I may be overlooking?
I'm fairly sure that the reason this happened is from checking ALL the check boxes in the format/wipe section of the custom recovery. After that these issues happened. Does that mean permabrick?
Related
Ok the web just glitched on me so this is the second time of me writing this novel and patience has grown very thin. First i would never be asking for this help if i didnt already do my 5 days of research and exhaust all solutions i can see. And since this is my second time writing this im sorry but im going to give the short version. I did the fatal mistake of lg style reset while i was rooted i know its a rookie mistake i thought i was completely unrooted and didnt double check it before i continued. i cant boot into recovery at all or if i can its just a black screen. when i boot normally it goes to the lg logo then to a black screen. i can access emergency mode however i cant get my pc ( running xp sp3 ) to recognize the device. I can get it to be recognized when i boot it normally to the black screen and even gain acces to root through adb, When in emergency i get nothing though and i have attempted recovery and flashing through adb, kdz, romtools, lgmdp and a few more randoms i could find in the forums ( i have done a lot of research ) when i do establish root though i cant seem to push or pull files, flash, mount or anything besides adb shell, the rest is filled with error: 0's and sbin/sh "whatever" not found, etc. since i can establish root it leads me to believe this can be fixed. THANK YOU in advance for any help you can throw my way and I'm sorry if this post is vague, poorly written ( like i said second time going through this ) or gets under your skin i know better that you veterans hate reading these posts and im only asking for help because now i am at my wits end. Thank you again
hey it would be nice if you could tell something about lg style reset and that rooted thing..... I don't have any info. about bricking the device like this.... ;-)
just wanted to know as a word of caution....
Sent from my LG-P500 using xda premium
I m not aware if lg p500/optimus one clockwork mod recovery will work on optimus v.
If recoveries of both phones are same you can follow http://forum.xda-developers.com/showthread.php?t=1318750 to install custom recovery of lg p500/optimus one from emergency mode.
fundoozzz said:
hey it would be nice if you could tell something about lg style reset and that rooted thing..... I don't have any info. about bricking the device like this.... ;-)
just wanted to know as a word of caution....
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Rooting is the process of essentially gaining Administrator rights to your phone ( So you can access files and gain privilages you wouldn't normally have ) Think of it like a computer and your signed in as a guest when you root your signed in as the Admin, Hope that helps. LG style reset is the factory reset of the phone from the recovery menu to restore the phone to its original state, Which is a huge no no while rooted or a custom recovery is installed.
mak.3736 said:
I m not aware if lg p500/optimus one clockwork mod recovery will work on optimus v.
If recoveries of both phones are same you can follow http://forum.xda-developers.com/showthread.php?t=1318750 to install custom recovery of lg p500/optimus one from emergency mode.
Click to expand...
Click to collapse
I attempted that and its a no go. The main problem being i can not get my phone to be recognized by the computer while it is emergency mode and i can not even select an image or anything. I booted it normally ( into the black screen i get after LG logo ) And i dont recieve a pop up with image and i recieve a error everytime i attempt to backup my nv its doesnt seem to be found, Nothing, but the device does get recognized at least.
AbattoirX said:
I attempted that and its a no go. The main problem being i can not get my phone to be recognized by the computer while it is emergency mode and i can not even select an image or anything. I booted it normally ( into the black screen i get after LG logo ) And i dont recieve a pop up with image and i recieve a error everytime i attempt to backup my nv its doesnt seem to be found, Nothing, but the device does get recognized at least.
Click to expand...
Click to collapse
Are you able to connect to phone from lgmdp when booted normally ( into the black screen you get after LG logo ).
If yes then
dont back up nv
no need the pop up window, press on "select image" in lgmdp and browse to recovery extracted folder for "image folder"
then press "start or download"
fix-black-screen-custom-recovery-custom-roms
I'd've posted it here on xda, too, but it's quite enough manainance dealing with it in one forum already.
the problem is that lg started shipping the optimus v with cheaper hitachi screens instead of the novatek screen it was released with. so the older custom recoveries and roms use a kernel that isn't configured to use the hitachi screen and you only get to see the backlight with no display.
edit:
mak.3736 said:
I m not aware if lg p500/optimus one clockwork mod recovery will work on optimus v.
If recoveries of both phones are same you can follow http://forum.xda-developers.com/showthread.php?t=1318750 to install custom recovery of lg p500/optimus one from emergency mode.
Click to expand...
Click to collapse
the p500 kernel is incompatible (different chipset.) so the recovery won't work even it the mtd map is the same.
bummer, as that's be a nice easy fix.
Mak Thank you for the progress i have made so far i did manage to get the phone connected through lgmpd as i have before however this was the first time when connected it went straight to emergency ready ( in the lgmpd screen ) I am going ahead to assume that is good i was never able to get it that far. The problem i face now when i press the "select image" button nothing happens, as long as the button is pushed down the word ready in the bottom left disappears and when released the word reappears, However i dont recieve the option to browse any menu for the image. Is there a specific folder i should have extracted to? I'll continue my research too if i find out the problem i wil post it immediately, Thank you again for your help i'm not there yet but definately making progress.
Squid, I knew about that topic too i remember reading it during my research, It must of slipped my mind before i even though about posting this. I'm Sorry ill be more careful about making these posts in the future
Also Squid since the chipsets are different i assume thats a no go, Would it still hurt to try? i'm running on hopes and dreams at the moment. Also when booted normally to my black screen i can obtain root access via adb leading me to believe if i can do that a fix is present somewhere
AbattoirX said:
...snip
Also Squid since the chipsets are different i assume thats a no go, Would it still hurt to try? i'm running on hopes and dreams at the moment. Also when booted normally to my black screen i can obtain root access via adb leading me to believe if i can do that a fix is present somewhere
Click to expand...
Click to collapse
yes, a no-go. when I flashed a p500 kernel to my v for experimental purposes, it wouldn't boot right for a day even after putting a working kernel back on it. it had to sit with the battery pulled for a few minutes between boots or it would just freeze on the lg logo.
if you follow the adb instructions to install a compatible recovery (currently, BobZhome IHO recovery is advised) in the thread I linked to, you should be fine.
AbattoirX said:
Mak Thank you for the progress i have made so far i did manage to get the phone connected through lgmpd as i have before however this was the first time when connected it went straight to emergency ready ( in the lgmpd screen ) I am going ahead to assume that is good i was never able to get it that far. The problem i face now when i press the "select image" button nothing happens, as long as the button is pushed down the word ready in the bottom left disappears and when released the word reappears, However i dont recieve the option to browse any menu for the image. Is there a specific folder i should have extracted to? I'll continue my research too if i find out the problem i wil post it immediately, Thank you again for your help i'm not there yet but definately making progress.
Click to expand...
Click to collapse
yes, as long as pressing the "select image" button ready in the bottom left disappears. But when you release button you should get a window poped up to select image folder.
Try again to connect in emergency mode and see.
AbattoirX said:
when i do establish root though i cant seem to push or pull files, flash, mount or anything besides adb shell, the rest is filled with error: 0's and sbin/sh "whatever" not found, etc.
Click to expand...
Click to collapse
I did follow those instructions previously ( 2 days ago i believe ) When i attempted that i was not able to push the needed files to my sd card unfortunately and i did try multiple times using Xionia recovery. I understand user error so I'll try again with a fresh mind just to be certain and get back to all of you.
AbattoirX said:
Rooting is the process of essentially gaining Administrator rights to your phone ( So you can access files and gain privilages you wouldn't normally have ) Think of it like a computer and your signed in as a guest when you root your signed in as the Admin, Hope that helps. LG style reset is the factory reset of the phone from the recovery menu to restore the phone to its original state, Which is a huge no no while rooted or a custom recovery is installed
Click to expand...
Click to collapse
I know what rooting is....infact I myself is on CM 6.5.8
what I didn't knew was that factory reset with custom recovery can brick our device..
but I feel this is not true as many people had done factory reset when they had problems after restoring nandroid backup....
I know a corrupted /system partition will cause the 'system/bin/sh not found' with adb if you're booting into the rom, I hadn't seen that booting into recovery.
if you have an older optimus v (2.2.1 froyo original, pv5 baseband) you can
Code:
adb reboot bootloader
to get to the bootloader and use fastboot to flash the recovery or even the whole system.
2.2.2 optimus v with pv7 firmware has the bootloader locked, so trying to reboot into the bootloader just tries to boot to the normal ROM.
My apologies Fundoozzz i was not insulting your intelligence just covering all basis, And from what i understand when you choose lg style reset from recovery it is the same as perform the factory reset from the settings menu which i guess your not suppose to. I by no means am not an expert on any of this obviously, I'm just simply relaying the information i have read on these and android forums as well as my personal experience.
Squid, I purchased this in the beginning of sept. and as i understand the revamped the Optimus in August?? So yes im running the later version and to double back on the posts I tried to push files again and attempted fastboot before still with the sbin/sh not found error....I am still hopeful that this is not a paper wieght however it very well could be thank you both again
have you tried booting into the blacked recovery before using adb?
(hold home+vol down while pressing power until lg logo goes black)
it sounds like your rom was corrupted (so adb is fairly useless there,) and recovery might be working but you just can't see it if you do have a newer OV.
to force reboot to recovery without the button-smashing,
adb reboot recovery
while you're booted normally.
then try adb again.
please cut/paste the errors you're getting with the commands you're using, here in this thread..
Well all be cheese and crackers, Thank you Squid it did the trick to actually push the image to my sd card here are the commands that I used....
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner>cd c:\android\platform-tools
C:\Android\platform-tools>reboot recovery
'reboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Android\platform-tools>adb shell
~ # reboot recovery
reboot recovery
C:\Android\platform-tools>adb push vm670nh_recovery.img /sdcard/
2608 KB/s (4200448 bytes in 1.572s)
C:\Android\platform-tools>
Now before i move further just to humor me all i need to do is push the flash_image and reboot to recovery and i should be good from there to flash a new rom. I ask only so i dont mess this up any worse than i have
if you're in the recovery, flash_image is already in the PATH.
Code:
adb shell
flash_image recovery /sdcard/vm670nh_recovery.img
exit
adb reboot recovery
then you should be ready to see your recovery.
format cache, data, and system.
install the rom.zip as usual.
THANK YOU VERY MUCH, How I wasn't able to obtain this I'm not too sure lack of knowledge or user errors possibly regardless I am now in CWM recovery and will format and flash my new rom. Any suggestions by the way? I was considering CM7 but i heard mixed reviews about it on the Optimus v. Oh well I'll do some research Thank you again Squid if i can repay this debt let me know, Lets face the facts in reality you just saved me over a hundred dollars and countless more headaches. Thank you again to everyone, much appreciated!
AbattoirX said:
THANK YOU VERY MUCH, How I wasn't able to obtain this I'm not too sure lack of knowledge or user errors possibly regardless I am now in CWM recovery and will format and flash my new rom. Any suggestions by the way? I was considering CM7 but i heard mixed reviews about it on the Optimus v. Oh well I'll do some research
Click to expand...
Click to collapse
I really enjoy the IHO cm7 flavors, all of them.
I advise giving one a whirl, froyo just doesn't compare to gingerbread for my personal use.
They use more battery than harmonia, but the features! the features!
Thank you again Squid if i can repay this debt let me know, Lets face the facts in reality you just saved me over a hundred dollars and countless more headaches. Thank you again to everyone, much appreciated!
Click to expand...
Click to collapse
if you're financially solvent, I have a donate button in the sidebar... I like to help people out, but my woman really appreciates it when I get more from helping than warm fuzzies.
the thanks are appreciated, though, and if your income is like mine, don't send any money
Well if a promise is worth anything in this day and age, when I am slightly more financially stable I'll send enough for a six pack your way or some flowers so your girl won't mind you helping us for a while longer Thanks again and I'll load up CM7 now
Well easy come and easy go back to a new LG screen. So after managing to get the recovery working i went to flash CM7 on the Optimus using information here http://androidforums.com/optimus-v-all-things-root/366620-cm7-installation-my-optimus-v.html Anyway I am now experiencing this problem, I get stuck back at the lg screen again. I did wipe the cache data system 3 times to be safe before flashing the rom and i only have access to emergency mode and this screen ( regular boot and recovery mode come up and end the exact same way ). I'll explain what i see step by step...
1. The black and silver LG Logo
2. A green Android guy next to a box with arrow coming out and these words come up on the screen. " with out the numbers of course "
(1) Android Recovery
(2) Do Not Pull Battery
(3) Formatting Data:...
(4) Formatting cache:...
(5) Factory Reset...
(6) Rebooting...
3. Then reboots back to the black and silver LG Logo screen.
4. Finally stops and freeze's up on the screen with a pinkish/reddish LG symbol with LG next to it and www.lgmobile.com written underneath it.
Question being is this some sort of recovery boot loop? And if it is what can be done about it? Furthermore many if not all files on the phone so far seem to be " read only " .... well i guess I'm ready for round two!
I rooted mah Prime (TY Viperboy and contributing dev's!) and finally installed Font Changer. After I selected the font I wanted, obviously I re-booted....and re-booted..and etc. My TFP won't get past the ASUS boot animation, the circle just keeps spinning and spinning. I tried wiping user data and still nothing. Does anyone have a similar experience or advice? I didn't change the density or anything else, just the font.
I also tried the reset button a few times just in case and still the same thing. Android Commander doesn't see it when I connect either, Windows tried to install drivers for it(which i've obviously already installed) and kept getting an error.
98 views...am I the only one who has used Font Changer on the TFP? Do any of you vets on here have an idea how I might be able to boot the device or at least completely revert it to all factory settings/apps? I apologize for having a one sided conversation, but I really would like to use mah Prime again. Thanks!
Sent from my SPH-M900 using XDA App
I use Font Changer and haven't had a problem yet.
Hmm...Well I opted to re-boot from Font Changer after I changed fonts. Did you do the same?
pappasquirrel said:
Hmm...Well I opted to re-boot from Font Changer after I changed fonts. Did you do the same?
Click to expand...
Click to collapse
Yes. I don't know what to tell you.
Anyone know if there is a file I could put on my sd card that the TFP would boot from, like how PG86IMG works w fastboot?
not sure, but i would suggest you to get the newest update from their site, then pop it on a micro sd, (or sd if you have the dock) and try holding power and vol up .... or maybe power vol down, dont remember..
now when you download the zip from asus site, make sure to unextract and copy the zip after you unextract. It's a zip in a zip.
Then try with the zip as its labeled, maybe it'll work or rename to update.zip.... that seems to be the norm on other devices.
good luck, i hope it works so we can have another solution for those that this happens to. Can't wait for unlocker tool, so we can get a recovery on this and if that ever happens we can just do a restore. good luck!
Good idea, thanks! I will give that a go and report back soon. I know I had this problem once or twice on my EVO3D and Moment, I would have to do something similar and try again. I'm hoping for good news to report
keep us updated, I am sort of in the same boat. Mine wont boot up after last firnware update and I have been searching to see if I can make it read the update file from SD
btw, try volume up with power, then hit volume down.... maybe it'll just do a recovery with the image it already has
damn i dont know if its volume up or down.... anyone ever tried this? i dont have my tab with me...to test
Its vol dwn+power for recovery. it will ask to press vol up within 5 sec to enter RCK, I've done that and "andy" just lays there on his back w an exclamation mark coming out of his chest.
If you wait, you get a screen with 10 seconds to select one of two options, User Data Wipe and linex cold boot. I've tried both with no avail. One more thing I found out is since my Prime just stays at the loading screen, everytime I hold power or reset button it would just reboot and hang there again. Aside from letting the battery die the only option I've found to shut down is hold vol up+power till it vibrates, keep em dwn for 2 more seconds and it will shut down.
Sent from my SPH-M900 using XDA App
Font Changer, now TFP won't boot.
My Asus Prime is in the same situation as yours. A rooted it and install Font Changer, after reboot my TFP won't get past the ASUS boot animation. I tryed all the things you do, but Android doesen´t start.
I install APX driver in Windows 7, and when i connect the USB cable, the device is reconized in Windows Device Manager, but a can not acess the tablet.
I don´t know a method the acess the Tablet from microSD, do you know ?
May be BOOTLOADER UNLOCK release from ASUS solve it.
Good luck for us.
Still nada. Windows will reconize that its plugged in, but I get a code 43 or code 10 and can't access the TFP in anyway (that I know of). I asked the same question over on Transformerforums.com and member leeshor has been really helpful. Most of the idea's I was given I had already tried or I could not get to work for my specific problem, but I'm sure that the info will be helpful for a lot of you guys. Here's a link to my thread, check leeshor's sig for some helpful tips. http://www.transformerforums.com/forum/transformer-prime-help/15428-font-changer-now-wont-boot.html
I'm still workin' on it and I'll post if I am able to make any progress, good luck!
Data wipe will definitely not work in this situation as it does nothing to the /System which is where the font's are stored. My best guess is that the font was changed but the permission was not correctly written, had this problem in the early days of my Desire HD.
The only solution that will work, is if you can get into an ADB shell and either put the original fonts back or change the permissions to the correct permissions.
Doktaphex said:
Data wipe will definitely not work in this situation as it does nothing to the /System which is where the font's are stored. My best guess is that the font was changed but the permission was not correctly written, had this problem in the early days of my Desire HD.
The only solution that will work, is if you can get into an ADB shell and either put the original fonts back or change the permissions to the correct permissions.
Click to expand...
Click to collapse
That's what I figured, I just can't get windows to recognize it. When I connect via USB and the device is off, windows sees it as an unknown device(obviously) and that the drivers are fine. After I power it up, windows will either recognize it as an MTP device and when I try to access the tab or re-install the drivers I get a code 10. Or it will still show up as an unknown device with an "!" giving me a code 43. Is there any other way I can gain root access?
It's been awhile (or seems so) and I still haven't had any success. Has anyone else made progress getting back to a usable device??
Ok, so before I send my prime in...do any of you smarty pants know (guess is fine) if this lil problem some of us are having will have a solution when ASUS unlocks the bootloader? Unless there is some kind of boot.zip err something that will load up from stock recovery, I don't think it will change anything. Thoughts? Advice? Bueller?? Thank you in advance
Sent from my SPH-M900 using XDA App
Unlock-bootloader.apk....I guess that answers my question to whether i'd be able to fix permissions from recovery :/ What am I not seeing? There has to be a way to get these Primes w no adb access and a stuck boot screen to fire up...?
Sent from my SPH-M900 using XDA App
Have you tried the blob file from SDcard trick. I believe you rename the update to EP201_SDUPDATE.zip and it should be able to run from the RCK. It has to be on a micro sdcard though otherwise it doesn't work apparently.
As outlined here:
http://forum.xda-developers.com/showpost.php?p=22743057&postcount=119
I received a G Tablet which had been used for development work for a few months. The person giving it to me (not the dev who has left) said the tablet was working fine, but had just become frozen at a reboot after he had tried to erase personal data from the tablet. I asked him if he had erased the sd card and he said "maybe" but that he couldn't remember. I powered the tablet on and sure enough it displayed two lines on a black background, one of which said something like loading kernel.
Now, these tablets were all rooted, and had Android 2.3 on them, via one of the ROMs discussed here. I don't know which one however.
So, I tried using NVflash to flash the tablet back to a stock ROM. Tablet then got stuck in a boot loop; I would see the Viewsonic logo, then the G Tablet logo, and then this would go on forever.
So I shut it down and tried again. This time Nvflash failed almost at the last step after having written most of the image.
And so here I am now, with a totally dead tablet. I cannot power it on. No combination of power or volume up/down buttons work. The only sign of life is when I plug it into its charger, and see the charging light come on.
I confirmed again with the person who gave me the tablet that the device was working just fine before it froze at a reboot after his erasing attempts.
Is there a way out of this? I hope so. Please help!
Thanks very much
Paul
texnote said:
I received a G Tablet which had been used for development work for a few months. The person giving it to me (not the dev who has left) said the tablet was working fine, but had just become frozen at a reboot after he had tried to erase personal data from the tablet. I asked him if he had erased the sd card and he said "maybe" but that he couldn't remember. I powered the tablet on and sure enough it displayed two lines on a black background, one of which said something like loading kernel.
Now, these tablets were all rooted, and had Android 2.3 on them, via one of the ROMs discussed here. I don't know which one however.
So, I tried using NVflash to flash the tablet back to a stock ROM. Tablet then got stuck in a boot loop; I would see the Viewsonic logo, then the G Tablet logo, and then this would go on forever.
So I shut it down and tried again. This time Nvflash failed almost at the last step after having written most of the image.
And so here I am now, with a totally dead tablet. I cannot power it on. No combination of power or volume up/down buttons work. The only sign of life is when I plug it into its charger, and see the charging light come on.
I confirmed again with the person who gave me the tablet that the device was working just fine before it froze at a reboot after his erasing attempts.
Is there a way out of this? I hope so. Please help!
Thanks very much
Paul
Click to expand...
Click to collapse
I would try popping it open and unplugging the internal battery then plugging it back in. Also hit the internal reset button while you're in there. It's pretty hard to actually kill one of these tablets. PM me if you need any other help.
help
Started my own thread, didnt mean to hijack. =)
Thanks, I will try removing the battery and let you know.
As for NVflash, I believe the latest version is here:
http://www.slatedroid.com/topic/171...-using-either-11-or-12-based-images-g-tablet/
However in my case I have no idea whether I have 1.1 or 1.2 and there is no way to determine this. Which one should I choose?
Paul
Doesn't matter for NVFlash, just download all of the flash files again because it might be that you have a bad download. Also make sure you have the right drivers installed since the drivers that automatically install when you plug it in sometimes don't work.
I'm pretty sure that if it boots past the birds, the hardware is working okay, so you should run the FORMAT version for NVFlash and then I'd run just a CWM flash setup and see if you can get into CWM and delete the partitions from within that.
The best thing to flash as far as ROMs would be Bekit's 1105 which is stock OTB with a few key changes. If you can't get the 1105 to play nice, you might really have some hardware problems.
I would go with the 1.2 BL, it will give you access to the newer roms as it appears that dev for the 1.1 BL seems to be dwindeling. I upgraded mine to 1.2 the other day and it worked great.
Alright. I need some advice one last time, I swear... after this I'm not going to try to do anything.
Phone worked quite well for 2 days. I was enjoying this rom quite a bit. I decided to change the DPI down to 560. I saw that some others in this thread had done so quite easily... so I used this app to change it. Made the change to 560, granted supersu permission and rebooted. Only problem is that... the phone has yet to turn back on. At the moment the only thing I can get it to do is give me a screen that shows a large white empty battery with a cable leading up to it and a hazard exclamation mark in the bottom right when I am trying to put it in download mode. I have tried on multiple computers to restore back to stock following these directions. The best that happens is my computer recognizes an unrecognized device. No luck.
I would love to change the buildprop back or anything, but not even adb recognizes the device.
Otherwise, nothing. I can't get into recovery. I can't get the phone to start at all. All black screen. I can't get any reaction out of it. Any advice would be helpful, I'm on hour two of this. I realize that this is most likely not a problem with the rom, but wanted to see if anyone else had an issue and has advice/let anyone else who's thinking of changing the DPI and shared my troubles reconsider.
Thanks again!
The empty the battery logo is because the phone is dead try charging it for like 30 mins. Also it seems that app you used is 3 years old so it does not support lollipop or even kitkat. After charging it try get it into recovery and restore a backup. If you don't have a backup try wiping your data and cache.
1619415 said:
The empty the battery logo is because the phone is dead try charging it for like 30 mins. Also it seems that app you used is 3 years old so it does not support lollipop or even kitkat. After charging it try get it into recovery and restore a backup. If you don't have a backup try wiping your data and cache.
Click to expand...
Click to collapse
Thanks for the reply!
That emblem only shows up when the battery is removed and I'm trying to put the phone in download mode. So it makes sense. Any other ideas? The battery that I'm using is about 80% full. I still can't find a way to recovery mode.
What other information can I provide to help you out?
Well when your in download mode it does not take any commands can you get the lg powered by android screen? Or just nothing happens? If nothing at all happenes it is most likly bricked. If it boots to the lg screen it is most likly soft bricked.
Bricked- Phone is dead and very very hard to fix if there is a fix
Soft Brick- No OS so you have to reinstall a rom could also be, because of apps.
1619415 said:
Well when your in download mode it does not take any commands can you get the lg powered by android screen? Or just nothing happens? If nothing at all happenes it is most likly bricked. If it boots to the lg screen it is most likly soft bricked.
Bricked- Phone is dead and very very hard to fix if there is a fix
Soft Brick- No OS so you have to reinstall a rom could also be, because of apps.
Click to expand...
Click to collapse
No screen. For anything (other than described).
This is exactly what I was afraid of, but my phone has always been odd. This dead battery screen has always shown up in download mode... even when my phone worked, I've never had the firmware update screen. Which has always been weird to me.
However, the only time my phone shows anything is with the dead battery screen. During such it will show up as an unrecognized device when attached to a computer, again... it's always done this. I was just curious if there was something else or a suggestion that someone more experienced then myself might have.
No that I read it, it sounds like there maybe a very slim chance of getting your device to work. If you mange to get some drivers for the unreconized device driver you maybe able to send adb and fastboot commands. I found this one tool (will limk below) that is call cydia impactor I found in one of rootjunky's toolkit files. I used this one function that was able to make drivers for my sony smartwatch 3 and phone. I will link for the direct download make sure to extract the zip. Inside of the zip you will find another zip called "Impactor_0.9.14.zip" make sure to extract it to it's own folder. If you want you can delete the first folder juat save the impactor folder. Then run the program called "Impactor" can connect your phone to the computer and click on the tab called "USB" then click the button called "Driver Scan". Follow any on screen instructions. It should now generate a driver for your phone if all went well and it will be reconized. Then you should be able to run adb reboot recovery or fastboot reboot-bootloader. The fact that your computer is even seeing the phone tells me that it has so hope of being fixed because your computer see's it. Your device might be in a bootloop of some sort. You may just have no os installed and it may have just glitched.
Download: http://rootjunkysdl.com/getdownload.php?file=Tegra Note 7/ADB root.zip (will immeditly download it)
Worst case scenario, you may try this, or at least read it for general info. I don't think you'll have to go this far though
http://forum.xda-developers.com/showthread.php?t=2582142
[FIX] NO Recovery mode, No download mode, after OTA on rooted LG G2
i changed my dpi once and it bootlooped on me. i was lucky enough to get into recovery and then i restored the data partition from an older nandroid.
i agree with 16. it does sound like the drivers may not be loaded up properly if your computer recognizes a device. have you tried the official lg drivers?
What system are you guys running?
Well, I've found out that for whatever reason... on my phone I have to take out the battery for a period of ~5-10 mins on any change DPI, system rom update, anything. Otherwise, my phone will not turn on. So if someone else find this, give it a try.
Hi hello
So here’s a head scratcher I hope someone can help me with that won’t involve replacing my main board.
Got myself the p20 lite (ANE-LX1 C432) - Single Sim.
I unlocked the bootloader with Huawei just before they stopped handing out the codes. All was good and happy with the world.
Rooted with Magisk and Was busy messing around With Termux, Linux deploy, Mobile Terminal and some pretty basic stuff. I’ve been out of the android scene for a while so was getting reacquainted with the scene.
Anyway. I was messing around in the terminal in a root shell just fixing basic permissions after messing up my termux environment as root. Phone randomly rebooted (I must’ve messed with the wrong folder -no idea which) came back on and my IMEI and baseband were gone.
No worries, I thought. Happened tonnes of times with my previous Devices (looking at you Samsung) just a quick restore or flash and all will be happy again.
Yeah, not quite.
Note that up until this point I hadn’t touched the system partition (probably besides the mobile terminal mishap -no idea)
So over the last week or so I have tried everything. Restore from Twrp backup. Flashed stock through fastboot, through erecovery. Those flashed ok but didn’t fix it.
Putting numerous different update.app FULL & OTA updates in dload folder on SD and internal all failed. Only used my builds version of course and only ones firmware finder deemed compatible/available
Then I got desperate (read: stupid) Decided to take the unpacked firmware files and flash whichever ones twrp would let me. First tried just the modem files. Didn’t help. Then just went through the list and flashed all I could.
I think the kicker came in when I installed the Trustfirmware.img because once I did that I rebooted and now I was stuck in an endless boot loop. No way to get into recovery. Not with their ton combo nor adb/fastboot.
I still had access to fastboot at this point at least and started doing every single thing suggested all over the net just trying to get back to stock.
Tried the unbrick option on The Huawei Multi-Tool. Flashed ok. Phone still wouldn’t boot. Did it a few times with 3 approved versions. Nothing. Only access to fastboot otherwise I was in a boot loop with error mode error no 15 and the verification failure (Attached below)
Last thing I tried after reading online was to relock my boot loader and flash stock. So I locked it with Huawei Multi-Tool. Reboot......
Now I don’t even have access to fastboot. My PC’s (windows and Linux) don’t even acknowledge it and holding volume down in all the weird and wonderful ways and times does nothing. All I get is startup Huawei Logo, Error Mode as per pic Below and then reboot. That’s it.
I’m assuming it’s trying to do a factory reset after relocking the bootloader (if it even locked properly, can’t check) but it can’t get into recovery/erecovery. I dunno ?
That’s my essay of where I’m at. Warranty is already void so not an option and I don’t want to buy a new mainboard (may as well buy a new phone).
So here I am. Is this my life now or does anyone have any magic tricks to possibly suggest?
Pyrolectic13 said:
Hi hello
So here’s a head scratcher I hope someone can help me with that won’t involve replacing my main board.
Got myself the p20 lite (ANE-LX1 C432) - Single Sim.
I unlocked the bootloader with Huawei just before they stopped handing out the codes. All was good and happy with the world.
Rooted with Magisk and Was busy messing around With Termux, Linux deploy, Mobile Terminal and some pretty basic stuff. I’ve been out of the android scene for a while so was getting reacquainted with the scene.
Anyway. I was messing around in the terminal in a root shell just fixing basic permissions after messing up my termux environment as root. Phone randomly rebooted (I must’ve messed with the wrong folder -no idea which) came back on and my IMEI and baseband were gone.
No worries, I thought. Happened tonnes of times with my previous Devices (looking at you Samsung) just a quick restore or flash and all will be happy again.
Yeah, not quite.
Note that up until this point I hadn’t touched the system partition (probably besides the mobile terminal mishap -no idea)
So over the last week or so I have tried everything. Restore from Twrp backup. Flashed stock through fastboot, through erecovery. Those flashed ok but didn’t fix it.
Putting numerous different update.app FULL & OTA updates in dload folder on SD and internal all failed. Only used my builds version of course and only ones firmware finder deemed compatible/available
Then I got desperate (read: stupid) Decided to take the unpacked firmware files and flash whichever ones twrp would let me. First tried just the modem files. Didn’t help. Then just went through the list and flashed all I could.
I think the kicker came in when I installed the Trustfirmware.img because once I did that I rebooted and now I was stuck in an endless boot loop. No way to get into recovery. Not with their ton combo nor adb/fastboot.
I still had access to fastboot at this point at least and started doing every single thing suggested all over the net just trying to get back to stock.
Tried the unbrick option on The Huawei Multi-Tool. Flashed ok. Phone still wouldn’t boot. Did it a few times with 3 approved versions. Nothing. Only access to fastboot otherwise I was in a boot loop with error mode error no 15 and the verification failure (Attached below)
Last thing I tried after reading online was to relock my boot loader and flash stock. So I locked it with Huawei Multi-Tool. Reboot......
Now I don’t even have access to fastboot. My PC’s (windows and Linux) don’t even acknowledge it and holding volume down in all the weird and wonderful ways and times does nothing. All I get is startup Huawei Logo, Error Mode as per pic Below and then reboot. That’s it.
I’m assuming it’s trying to do a factory reset after relocking the bootloader (if it even locked properly, can’t check) but it can’t get into recovery/erecovery. I dunno ?
That’s my essay of where I’m at. Warranty is already void so not an option and I don’t want to buy a new mainboard (may as well buy a new phone).
So here I am. Is this my life now or does anyone have any magic tricks to possibly suggest?
Click to expand...
Click to collapse
Check the second post in this thread:
https://forum.xda-developers.com/honor-7x/help/help-stuck-error-mode-screen-t3735067
kilroystyx said:
Check the second post in this thread:
https://forum.xda-developers.com/honor-7x/help/help-stuck-error-mode-screen-t3735067
Click to expand...
Click to collapse
Thanks for this.
The battery discharged fully about two days ago.
I haven’t tried plugging it in and out as/if it turns on immediately (though even though it shows dead without charger it still comes on immediately).
I’m gonna get a weaker lower amp charger and see if that maybe helps. Fml ?
***UPDATE***
Been at it for hours. Battery is completely flat. But h second I plug it in the the Black Huawei logo comes up ten a few seconds later it’s on the same error screen for a little longer then boot loops like that constantly.
The error isn’t the same as the post in that link though. And I am FRP unlocked.
Eh.
Pyrolectic13 said:
Thanks for this.
The battery discharged fully about two days ago.
I haven’t tried plugging it in and out as/if it turns on immediately (though even though it shows dead without charger it still comes on immediately).
I’m gonna get a weaker lower amp charger and see if that maybe helps. Fml ?
***UPDATE***
Been at it for hours. Battery is completely flat. But h second I plug it in the the Black Huawei logo comes up ten a few seconds later it’s on the same error screen for a little longer then boot loops like that constantly.
The error isn’t the same as the post in that link though. And I am FRP unlocked.
Eh.
Click to expand...
Click to collapse
I guess your previous error was related to ramdisk...
Now what is your current situation?
-What error is showed in the Error mode?
-Can you reach FASTBOOT&RESCUE MODE menu?
-What is your current recovery?
kilroystyx said:
I guess your previous error was related to ramdisk...
Now what is your current situation?
-What error is showed in the Error mode?
-Can you reach FASTBOOT&RESCUE MODE menu?
-What is your current recovery?
Click to expand...
Click to collapse
As it stands I cannot enter fastboot or recovery mode. Update from SD also doesn’t do anything. Battery is completely discharged. And if I leave it on the charger it doesn’t charge, only boot loops.
So with all that the ONLY thing this phone does now is:
- Starts up Showing Huawei logo
- Error Mode Screen with Func No: 15 (bl31 image) & Error No: 1 (security verify failed)
- Reboots
Ths happens whether it’s plugged into the pc’s usb or the charger. Tried all combinations of buttons too.
It has stock recovery as I flashed that back when trying to revert back to stock.
I lost access to fastboot after I locked the bootlaoder again using the Huawei Multi Tool. It’s like it trying to do the factory wipe that it usually would after locking/unlocking the bootloader but is unable to due to the error mode screen.
Sent from my iPhone using Tapatalk
Pyrolectic13 said:
As it stands I cannot enter fastboot or recovery mode. Update from SD also doesn’t do anything. Battery is completely discharged. And if I leave it on the charger it doesn’t charge, only boot loops.
So with all that the ONLY thing this phone does now is:
- Starts up Showing Huawei logo
- Error Mode Screen with Func No: 15 (bl31 image) & Error No: 1 (security verify failed)
- Reboots
Ths happens whether it’s plugged into the pc’s usb or the charger. Tried all combinations of buttons too.
It has stock recovery as I flashed that back when trying to revert back to stock.
I lost access to fastboot after I locked the bootlaoder again using the Huawei Multi Tool. It’s like it trying to do the factory wipe that it usually would after locking/unlocking the bootloader but is unable to due to the error mode screen.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I see, it is really bad
My last hope is to be able to do a forced Firmware upgrade. Press power button and VOL + and VOL- simultaneously. Do you see the same as the attached image?
kilroystyx said:
I see, it is really bad
My last hope is to be able to do a forced Firmware upgrade. Press power button and VOL + and VOL- simultaneously. Do you see the same as the attached image?
Click to expand...
Click to collapse
Ah man, I wish it would even do that. It makes no attempt to even pretend to see the sd card update. If I hold all the buttons in it still only comes up with the error mode and reboots.
I popped it open and connected a charger up battery to see if that would help but it doesn’t.
Do you maybe know the pin layout on the inside or know where I could get schematics? Been looking everywhere.
I’m almost done building my own Jtag box and am hoping to bring it back to life by writing straight to the damn thing.
Sent from my iPhone using Tapatalk
Pyrolectic13 said:
Ah man, I wish it would even do that. It makes no attempt to even pretend to see the sd card update. If I hold all the buttons in it still only comes up with the error mode and reboots.
I popped it open and connected a charger up battery to see if that would help but it doesn’t.
Do you maybe know the pin layout on the inside or know where I could get schematics? Been looking everywhere.
I’m almost done building my own Jtag box and am hoping to bring it back to life by writing straight to the damn thing.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
That is sad!!!
With JTAG and schematics stuff I cannot help you.
What I found recently and it was new for me (I didn't tested yet) is a possibility to install firmware via "dload" folder, but to start installation the stock recovery have to be full functional.
If I found something interesting for you I'll post here.
kilroystyx said:
That is sad!!!
With JTAG and schematics stuff I cannot help you.
What I found recently and it was new for me (I didn't tested yet) is a possibility to install firmware via "dload" folder, but to start installation the stock recovery have to be full functional.
If I found something interesting for you I'll post here.
Click to expand...
Click to collapse
To my knowledge the recovery is installed. Well erecovery. It was working up until I locked the bootloader again and it went into a boot loop instead of doing the factory reset.
Is there any other way to force sd update other than with the dload folder?
Thanks for tying to help, I appreciate it.
Pyrolectic13 said:
To my knowledge the recovery is installed. Well erecovery. It was working up until I locked the bootloader again and it went into a boot loop instead of doing the factory reset.
Is there any other way to force sd update other than with the dload folder?
Thanks for tying to help, I appreciate it.
Click to expand...
Click to collapse
You can check the official documentation about that.
Please let us know how you solved this problem.
kumarsid7 said:
Please let us know how you solved this problem.
Click to expand...
Click to collapse
Still unsolved as of yet.
I’ve finished building my own version of the Riff/Octoplus box as well as a makeshift Jtag. I’m still trying to find and piece together some firmware files and other board software I think I need.
Also, if anyone has any idea where the test point is on this board I’d really appreciate you pointing it out. I cannot find the schematics or any solid documentation anywhere.
I will attach the pics I have of both sides of the board as soon as I get home.
Sent from my iPhone using Tapatalk
in first picture youle see many circles golden 2 smallest is testpoint good luck
Pyrolectic13 said:
Still unsolved as of yet.
I’ve finished building my own version of the Riff/Octoplus box as well as a makeshift Jtag. I’m still trying to find and piece together some firmware files and other board software I think I need.
Also, if anyone has any idea where the test point is on this board I’d really appreciate you pointing it out. I cannot find the schematics or any solid documentation anywhere.
I will attach the pics I have of both sides of the board as soon as I get home.
View attachment 4579956
View attachment 4579957
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
in first picture youle see many circles golden 2 smallest is testpoint good luck
well, try to restore your device using dload method. It needs you to copy the UPDATE.APP in dload folder of an external sd card(formated in NTFS format) and then just press both vol up+down along with power button for a few seconds. It will auto launch huawei e-recovery and will try to flash the UPDATE.APP you stored in ext sd card. This should definitely work.
Dload method doesn't need you to unlock your device or bootloader.
Maybe?
I know it’s a long shot but I still have this phone. If anyone maybe knows if there’s been a way to fix this as of yet please let me know. ?
Lol. Still got this damn thing. Been searching around and seen a few people reporting similar errors. Never find out if they ever solve it though.
So. Anyone maybe have any knowledge to share? Anything at all.
I don't know if you still have your device, but I had the exact same issue with a P10 (VTR-L09)
I was able to fix fastboot using https://github.com/mashed-potatoes/PotatoNV
That tool was designed to unlock the bootloader, but I noticed that It actually flashes a slightly modified version of fastboot.
PotatoNV can also unlock P20 lite bootloader, so you should give it a shot.
Good luck!
If it works, you should be able to flash stock recovery image and then restore the system using the dload folder.
you can Repair it with Software Testpoint and Full Bootloader Unlock ,and then flash a Board Software via Software Testpoint, that helps 100%!!!
use this Firmware Download ANE-LX1
use the Software with logins and you have all what you need.
you must start the Software Testpoint so!!
VIDEO : how to start Software Testpoint P20 Lite
than in Software Testpoint you flash the included Board Software with DC-Phoenix and after that use the included dload update via sdcard and eRecovery mode and your Phone is running!!!
I would unlock the bootloader via Software Testpoint with DC-Phoenix, then the FBLock is unlocked and you can flash as you wish!!!! And the great thing about it is that you don't need an UnlockKey either, you can then read this with HCU client software, the only thing that's stupid is that you need a time-based license for the two programs, which you have to buy.
HCU client download
https://hcu-client.com
DC Phoenix download
https://forum.dc-unlocker.com/forum/modems-and-phones/huawei/155916-dc-phoenix
Since I accidentally bought a 3-day license twice and my P20 Lite is now completely rooted on Lineage 19.1, I can give away 2 access data, which are still valid for 2 days.
you can edit your smartphone with it.
username : bl26457
password : kKncnkMj
username : bl26390
password : JDAZqnkN
Then I wish you a lot of fun with it, hope it helps you if someone else is active in this thread.