FTV 2015, sloane-5.2.4.0-rooted_r1 rom, bricked flashing Magisk 12 in drunken stupor - Fire TV Q&A, Help & Troubleshooting

Hi All,
I managed to brick my Fire TV 2 by flashing Magisk 12 whilst under the influence.
The unit now boots to the white Amazon logo, the power light goes from white to orange and then it restarts (bootloop).
I have tried various fixes covered on the AFTV site to get back in to recovery but to no avail.
Attempted to re-root the unit which fails with the message "error: source file is larger than target file!"
During the re-root process, It does load the preloader and the power light pulses white until I remove the power lead. Is there anything I can do from here?
Details: sloane-5.2.4.0-rooted_r1 rom with TWRP recovery v3.0.0-5
Thanks.

Reflash the pre rooted rom from recovery

m1steron said:
Hi All,
I managed to brick my Fire TV 2 by flashing Magisk 12 whilst under the influence.
The unit now boots to the white Amazon logo, the power light goes from white to orange and then it restarts (bootloop).
I have tried various fixes covered on the AFTV site to get back in to recovery but to no avail.
Attempted to re-root the unit which fails with the message "error: source file is larger than target file!"
During the re-root process, It does load the preloader and the power light pulses white until I remove the power lead. Is there anything I can do from here?
Details: sloane-5.2.4.0-rooted_r1 rom with TWRP recovery v3.0.0-5
Thanks.
Click to expand...
Click to collapse
The 2nd main requisite for Magisk is a fully unlocked bootloader. And only a small % of FTV1's have this done. If you can still go into TWRP. Then just flash the same PreRooted ROM you had installed before.

Y314K said:
The 2nd main requisite for Magisk is a fully unlocked bootloader. And only a small % of FTV1's have this done. If you can still go into TWRP. Then just flash the same PreRooted ROM you had installed before.
Click to expand...
Click to collapse
Sorry but it's a Fire TV 2 and the problem is that I can't get in to the TWRP recovery. I have tried multiple methods including the remote button presses and keyboard combinations.
The device isn't recognised over a network or USB adb. Before I bricked it, both USB and ADB debugging were enabled.

Have you tried the unbrick method?.
https://forum.xda-developers.com/newreply.php?do=newreply&p=65281865
I unbricked mine this morning

CFKod said:
Have you tried the unbrick method?.
https://forum.xda-developers.com/newreply.php?do=newreply&p=65281865
I unbricked mine this morning
Click to expand...
Click to collapse
Yes I have tried this but receive the following error:
error: source file is larger than target file!
I have tried using different versions of recovery and installer.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: Your links didn't work properly. Wasn't until I looked at it again that I saw the bit about an unbrick image. Trying it now, fingers crossed...

OK, I have tried using both unbrick methods (unbrick.img and unbrick+ramdisk.img) they completed successfully but didn't resolve the issue (white Amazon logo, pulsing orange light bootloop).
Presently I am trying to inject the prerooted rom's boot.img using the "mediatek_inject firetv2 COM4 boot.img /boot -" command. At 4% so far...

Success! It took about 5 hours to flash the boot.img. Upon restarting the device it loaded to the white Amazon logo with the glowing white power led but this time it didn't reboot (no yellow light). It seemed stuck at this point so I started pressing the keyboard recovery buttons and viola, it opened TWRP. Flashed the latest pre-rooted rom, cleared caches and rebooted. Happily, all my data and apps were unaffected.
A lesson learnt. Don't mess about with technical things when you are drunk!
Thanks for all your help.

m1steron said:
Success! It took about 5 hours to flash the boot.img. Upon restarting the device it loaded to the white Amazon logo with the glowing white power led but this time it didn't reboot (no yellow light). It seemed stuck at this point so I started pressing the keyboard recovery buttons and viola, it opened TWRP. Flashed the latest pre-rooted rom, cleared caches and rebooted. Happily, all my data and apps were unaffected.
A lesson learnt. Don't mess about with technical things when you are drunk!
Thanks for all your help.
Click to expand...
Click to collapse
Thanks have wondered about magisk as more apps check root. Obviously a no no
Sent from my SM-G955F using Tapatalk

m1steron said:
Success! It took about 5 hours to flash the boot.img. Upon restarting the device it loaded to the white Amazon logo with the glowing white power led but this time it didn't reboot (no yellow light). It seemed stuck at this point so I started pressing the keyboard recovery buttons and viola, it opened TWRP. Flashed the latest pre-rooted rom, cleared caches and rebooted. Happily, all my data and apps were unaffected.
A lesson learnt. Don't mess about with technical things when you are drunk!
Thanks for all your help.
Click to expand...
Click to collapse
Just think you did some Magisk v12 on non-Unlocked Bootloader FTV test. I am just glad you at least got your device back to a normal state. Took one for the modding scene. Thanks drunken M1steron. I know sober M1steron would not have approved.

Hello m1steron,
Thxs for sharing your experience.
Krgds

m1steron said:
Success! It took about 5 hours to flash the boot.img. Upon restarting the device it loaded to the white Amazon logo with the glowing white power led but this time it didn't reboot (no yellow light). It seemed stuck at this point so I started pressing the keyboard recovery buttons and viola, it opened TWRP. Flashed the latest pre-rooted rom, cleared caches and rebooted. Happily, all my data and apps were unaffected.
A lesson learnt. Don't mess about with technical things when you are drunk!
Thanks for all your help.
Click to expand...
Click to collapse
Trying to flash boot.img the forth time using mediatek inject command... It stucks at around 50% each time. Should i try it again and again or leave it?

Servet83 said:
Trying to flash boot.img the forth time using mediatek inject command... It stucks at around 50% each time. Should i try it again and again or leave it?
Click to expand...
Click to collapse
Did it finish? I left mine flashing for most of the day so I don't know if it paused at 50% or not.

m1steron said:
Did it finish? I left mine flashing for most of the day so I don't know if it paused at 50% or not.
Click to expand...
Click to collapse
No, it didn't finish. Yesterday it stopped at 67%. Don't know what to do alternatively...is it cause im using a windows pc?

Servet83 said:
No, it didn't finish. Yesterday it stopped at 67%. Don't know what to do alternatively...is it cause im using a windows pc?
Click to expand...
Click to collapse
I used Windows 10 on an old works laptop. Could you describe all the steps you are taking?

m1steron said:
I used Windows 10 on an old works laptop. Could you describe all the steps you are taking?
Click to expand...
Click to collapse
1. Connect to FTV using a2a usb cable
2. start handshake
3. Power on Box (handshake complete)
4. Start mediatek inject command (continue with 'y')
5. Wait writing filesystem...
Here are 2 Screenshots. One for the install_firetv2_recovery process and the other dor mediatek inject process.

Servet83 said:
1. Connect to FTV using a2a usb cable
2. start handshake
3. Power on Box (handshake complete)
4. Start mediatek inject command (continue with 'y')
5. Wait writing filesystem...
Here are 2 Screenshots. One for the install_firetv2_recovery process and the other dor mediatek inject process.
Click to expand...
Click to collapse
Thanks, are you using the extracted boot.img from the same pre-rooted rom that is installed on your device?
Also, this is where I got the information from: https://forum.xda-developers.com/fire-tv/development/firetv-2-unbrick-image-t3313349/page3
rbox should be able to help.

m1steron said:
Thanks, are you using the extracted boot.img from the same pre-rooted rom that is installed on your device?
Also, this is where I got the information from: https://forum.xda-developers.com/fire-tv/development/firetv-2-unbrick-image-t3313349/page3
rbox should be able to help.
Click to expand...
Click to collapse
Yes, i am using the same boot.img (5.2.1.1).
How did u solve the error "source file larger target file" while running the install recovery batch?
Trying to get in touch with rbox. Thank u so far!

Servet83 said:
Yes, i am using the same boot.img (5.2.1.1).
How did u solve the error "source file larger target file" while running the install recovery batch?
Trying to get in touch with rbox. Thank u so far!
Click to expand...
Click to collapse
I didn't so I tried the below:
m1steron said:
OK, I have tried using both unbrick methods (unbrick.img and unbrick+ramdisk.img) they completed successfully but didn't resolve the issue (white Amazon logo, pulsing orange light bootloop).
Presently I am trying to inject the prerooted rom's boot.img using the "mediatek_inject firetv2 COM4 boot.img /boot -" command. At 4% so far...
Click to expand...
Click to collapse

m1steron said:
I didn't so I tried the below:
Click to expand...
Click to collapse
Didn't work for me i remember that usb debugging was turned of before bricking the device and maybe thats the issue now...

Related

[GUIDE]How to unbrick your Defy and solve other bugs

So your Defy is bricked. It's really hard to brick a Defy or a Defy+ due to locked bootloader, so you can't really brick it but you can get it in state of not booting. In this simple guide i will show you how to unbrick Defy and fix some common errors!
Lets get started!
How to unbrick your Defy
What do you need!
You need the following:
Motorola Defy
RSD Lite (download here: http://goo.gl/KRSRp
SBF (i reccomend 2.2 CEE Froyo) (download here: http://goo.gl/Jhz84) (for other SBFs use this link: http://goo.gl/dYQTl )
USB Cable
Charged battery (at least 50%)
Motorola USB Drivers (download here: http://goo.gl/bWg1M )
Download and install USB Drivers
Download and install RSD Lite
Turn off your phone
Go into bootloader by pressing Power button and Vol+ button
Connect your phone to your PC via USB cable
Make sure everything is OK
Locate downloaded SBF. In popup dialog press Uncompress and start flashing
If you get " Please manually power up this phone " in RSD Lite pull battery out > put your battery back > reboot into stock recovery by holding Power button and Vol- button > Choose Wipe data/cache > Choose Reboot system now
That's it, you unbricked your Defy!
How to repair damaged Dalvik or cache
Use the same method for unbricking your Defy. If you still have problems...do the same procedure again.
How to fix empty battery
If your battery is so empty that you can't even charge it, there are 2 options
Option 1. (McGyver method)
Get a USB cable, cut the off the B plug (the one that plugs into the device) and strip away the shielding, revealing the 4 individual wires inside: White, Green, Red and Black. Red is +5V DC and Black is ground. strip a few (1-2) mm's off each and gently push them into the + and - slots on the battery. Apply some tape to keep them in place, but don't cover the other connectors. Now plug the battery back in, a tight fit, but possible if you've peeled back the shielding and the white and green wires so that only Black and Red are actually being crammed in there with the battery
It should look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Red goes to the + terminal,Black goes to the - terminal
Plug the business end of the newly modded usb cable into your computer.
That's it, your Defy should be alive now
McGyver method found at this thread:http://forum.xda-developers.com/showthread.php?t=892026
I was lazy to write the method by my words...so i just copied from that thread....because he wrote it so well
If original author has problems with copyrights, he can PM me and we will sort it out.
Option 2.
Connect Defy to PC via USB cable. Make sure that your PC is powered on. LED in the top left-hand corner should be white coloured. Leave the Defy overnight to charge. In the morning it should be charged a little bit to charge it via normal method
I have not tested McGyver method, but option 2 worked for me (happened to me once)
This is the end of this tutorial. I hope i helped!
Froyo nandroid backup here
Guys I created a prerooted and with cwm installed froyo nandroid backup. Make full restore
Link: http://d-h.st/RxH
IF YOU DO MAKE ANY DAMAGE TO YOUR PHONE DURING THE PROCESS I AM NOT RESPONSIBLE!
is cee froyo recommended for india defy with stock froyo 2.2.2 and green lens?
my stock was retail taiwanese JRDNEM_U3_3.4.3-36-1.7_CHINESE_SIGN_SIGNED_UCAJRDNEMARAB1B50AA03A.0R_PDS03C_USAJRDNFRYORTINT15_P002_A014_HWp3_Service1FF.sbf.gz
reply please.
prax31 said:
is cee froyo recommended for india defy with stock froyo 2.2.2 and green lens?
my stock was retail taiwanese JRDNEM_U3_3.4.3-36-1.7_CHINESE_SIGN_SIGNED_UCAJRDNEMARAB1B50AA03A.0R_PDS03C_USAJRDNFRYORTINT15_P002_A014_HWp3_Service1FF.sbf.gz
reply please.
Click to expand...
Click to collapse
Well try it...you can always go back by flashing another SBF
IF YOU DO MAKE ANY DAMAGE TO YOUR PHONE , I AM NOT RESPONSIBLE!
bricked/not booting defy
basically downloaded & flashed a wrong sbf file after i rooted it from rsd lite. now its stuck at M screen, will not connect to rsd lite and i have searched relentlessly to figure out another way to flash to it, even in recovery mode will not unzip any files. is there a way to fix it? i have wiped cache and data and rebooted. nothing works...pls help :'(
melowed said:
basically downloaded & flashed a wrong sbf file after i rooted it from rsd lite. now its stuck at M screen, will not connect to rsd lite and i have searched relentlessly to figure out another way to flash to it, even in recovery mode will not unzip any files. is there a way to fix it? i have wiped cache and data and rebooted. nothing works...pls help :'(
Click to expand...
Click to collapse
Pull battery out and wait 5 minutes and reinsert it.
Sent from my house via interwebs to You!
bricked/not booting defy
ppero196 said:
Pull battery out and wait 5 minutes and reinsert it.
Sent from my house via interwebs to You!
Click to expand...
Click to collapse
tried that, still not working
melowed said:
tried that, still not working
Click to expand...
Click to collapse
Go manually to bootmenu (stock) and then connect phone with RSD Lite and flash another SBF
Sent from my house via interwebs to You!
bricked/not booting defy
ppero196 said:
Go manually to bootmenu (stock) and then connect phone with RSD Lite and flash another SBF
Sent from my house via interwebs to You!
Click to expand...
Click to collapse
i can get it to go to boot menu but it wont connect to rsd lite for me to flash another sbf. is there some other way im not aware of?
I can send you my froyo nandroid backup. You can restore it via CWM
No apps installed...it comes pre rooted. OK?
Sent from my house via interwebs to You!
bricked/not booting defy
ppero196 said:
I can send you my froyo nandroid backup. You can restore it via CWM
No apps installed...it comes pre rooted. OK?
Sent from my house via interwebs to You!
Click to expand...
Click to collapse
Awesome thx see if that works
FINALLY got it back to stock after upgrading to the the 5.9v of rsd lite and reinstalling the drivers but i had to flash the same sbf file about 4 times...lol i knew i had the right one but thanks for trying to help me anyway!
i need help asap
melowed said:
Awesome thx see if that works
FINALLY got it back to stock after upgrading to the the 5.9v of rsd lite and reinstalling the drivers but i had to flash the same sbf file about 4 times...lol i knew i had the right one but thanks for trying to help me anyway!
Click to expand...
Click to collapse
Can you send me also the froyo back up? this is what happened to me:
i cleared the cache in the bootloader menu
then i restore factory settings
then i had a zip file of a rom , i changed its name to update so that the bootloader can detect the update.. the update installed completely but when i started rebooting its just stuck at the "Motorola" logo.. what can i do to fix this sir?
drakefrancis said:
Can you send me also the froyo back up? this is what happened to me:
i cleared the cache in the bootloader menu
then i restore factory settings
then i had a zip file of a rom , i changed its name to update so that the bootloader can detect the update.. the update installed completely but when i started rebooting its just stuck at the "Motorola" logo.. what can i do to fix this sir?
Click to expand...
Click to collapse
OK..I'll send you...
It comes with 2ndinit and prerooted
Sent from my MB526 using xda app-developers app
ppero196 said:
OK..I'll send you...
It comes with 2ndinit and prerooted
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
Hey ppero, Thanks for the guide.
Some random Chinese build finally worked for my phone, phone was bough used: http://forum.xda-developers.com/showpost.php?p=14762402&postcount=143
Froyo nandroid backup
Extract in the root of SD card and restore using cwm
Make full restore
http://d-h.st/RxH
Sent from my iPhone 5 using Tapatalk 2
bricked MB526 BL7 no recovery available
Hello, I try to give as much information as possible so please bear with me.
MB526 with BL7 was working perfectly with the quarx nightly 20121018+update v3 but of course I installed the v4 update. What a friend and I figured is that there is a problem when flashing the 2ndboot updates with your power plug still plugged in, this is what I totally forgot about on the v4 update. I wiped the cache and dalvik before AND after the update but was stuck the bootloop. Now I had just made a CWM backup two weeks ago but when restoring I got an error message concerning the system folder. Still in bootloop on the splah M logo. I remember there was something about an older custom ROM and the recovery I used that didnt work so I figured I should start from the SBF.
Using RSDlite 5.7 on a winXP machine, I tried to flash the way I am used to flash brand new MB526 with BL7: (did that for a few friends and the girl)
1. DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
2. DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.sbf
but the plan was overthrown by my phone. It flashed through the whole process but was stuck at the the "please manually power up this phone"-screen in RSDlite, the phone was connected but at the splash screen. Battery out, the PASS would only appear in RSD if I boot directly into bootloader again. Otherwise this splash screen makes my mad. It doesnt boot.
I tried to flash the alternative, chinese, root ROM for BL7; samesame, but different.
Downloaded RSDlite 6.14, Mdriver 5.9 on a win7 machine, used about all the BL7 ROMs I could find on the site: sbf.droid-developers.org/umts_jordanplus/ The last one being the [Retail British] sbf.droid-developers.org/umts_jordanplus/DEFYPLUS_U3_4.5.1-134_DFP-231_BLUR_SIGN_USADEFYEMARAB1B8RTGB005.0R_PDS03C_USAJRDNGIBRRTGB_P023_A025_M002_Service1FF.sbf.gz
samesame
:crying:
Now I cannot boot into the motorola recovery. Theres just the background picture but no menu. As far as I know, flashing an SBF is all that I can do. Anyone has got an idea, which ROM to try or what else to do ?
Thanks in advance
butcherr said:
Hello, I try to give as much information as possible so please bear with me.
MB526 with BL7 was working perfectly with the quarx nightly 20121018+update v3 but of course I installed the v4 update. What a friend and I figured is that there is a problem when flashing the 2ndboot updates with your power plug still plugged in, this is what I totally forgot about on the v4 update. I wiped the cache and dalvik before AND after the update but was stuck the bootloop. Now I had just made a CWM backup two weeks ago but when restoring I got an error message concerning the system folder. Still in bootloop on the splah M logo. I remember there was something about an older custom ROM and the recovery I used that didnt work so I figured I should start from the SBF.
Using RSDlite 5.7 on a winXP machine, I tried to flash the way I am used to flash brand new MB526 with BL7: (did that for a few friends and the girl)
1. DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
2. DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.sbf
but the plan was overthrown by my phone. It flashed through the whole process but was stuck at the the "please manually power up this phone"-screen in RSDlite, the phone was connected but at the splash screen. Battery out, the PASS would only appear in RSD if I boot directly into bootloader again. Otherwise this splash screen makes my mad. It doesnt boot.
I tried to flash the alternative, chinese, root ROM for BL7; samesame, but different.
Downloaded RSDlite 6.14, Mdriver 5.9 on a win7 machine, used about all the BL7 ROMs I could find on the site: sbf.droid-developers.org/umts_jordanplus/ The last one being the [Retail British] sbf.droid-developers.org/umts_jordanplus/DEFYPLUS_U3_4.5.1-134_DFP-231_BLUR_SIGN_USADEFYEMARAB1B8RTGB005.0R_PDS03C_USAJRDNGIBRRTGB_P023_A025_M002_Service1FF.sbf.gz
samesame
:crying:
Now I cannot boot into the motorola recovery. Theres just the background picture but no menu. As far as I know, flashing an SBF is all that I can do. Anyone has got an idea, which ROM to try or what else to do ?
Thanks in advance
Click to expand...
Click to collapse
Flash the sbf again.
If you encounter please manually power up the phone unplug the device from PC, reboot into stock recovery and wipe data/factory reset. After that reboot
Trolls, trolls everywhere
ppero196 said:
Flash the sbf again.
If you encounter please manually power up the phone unplug the device from PC, reboot into stock recovery and wipe data/factory reset. After that reboot
Trolls, trolls everywhere
Click to expand...
Click to collapse
thank you. stock recovery. there is no stock recovery. MB526. BL7. Just the droid and a triangle with the "!" inside the triangle if I try to boot into stock recovery. I remember having this problem with my hannspad and there was a flashable ROM with just the stock recovery. Is there something comparable for the defy? only the recovery or is the BL7 the problem here?
butcherr said:
thank you. stock recovery. there is no stock recovery. MB526. BL7. Just the droid and a triangle with the "!" inside the triangle if I try to boot into stock recovery. I remember having this problem with my hannspad and there was a flashable ROM with just the stock recovery. Is there something comparable for the defy? only the recovery or is the BL7 the problem here?
Click to expand...
Click to collapse
That is Stock recovery (droid and yellow triangle) .Try pressing Vol Up and Vol Down simultaneously to get the menu. If that doesn't work TAP in the lower right hand corner of the screen to get the menu. Tap around a bit to get the right spot.
The newer stock recovery works off touch screen instead of the rocker buttons.
_ossie_ said:
That is Stock recovery (droid and yellow triangle) .Try pressing Vol Up and Vol Down simultaneously to get the menu. If that doesn't work TAP in the lower right hand corner of the screen to get the menu. Tap around a bit to get the right spot.
The newer stock recovery works off touch screen instead of the rocker buttons.
Click to expand...
Click to collapse
Thank you VERY much. I spent too much time with CWM it appears. I dont remember having used the stock recovery once. I thought BL7 was my enemy with that screen. My phone must feel like its been gangbangraped now with all the different ROMS I have flash upon it. Thanks again, quarx build 20121018+v4 running. Am creating a backup right now.
When I connect to pc (battery empty) it charges white led then boots up hangs on motorola logo for sometime then shutsdown to white led again, is that normal?

Noob needs help with fixing cyanogen boot loop

Hi everyone,
I bought my HTC One X today and was told to install Cyanogen Mod 10 on it to get the best out of it. I have followed a couple of guides but i have completely screwed this up!! After following the instructions (well thought i did anyway) i have gotten to the point where my phone is stuck in the boot loop (spinning circle thing).
I have tried following guides everywhere but i'm getting completely lost and getting more and more frustrated because i dont understand anything that is being explained.
So is there any way of getting my phone back to normal or some form of working condition because i would hate to have broken something i just bought within 7 hours of having it
Any help is much appreciated.
FXhnd77 said:
Hi everyone,
I bought my HTC One X today and was told to install Cyanogen Mod 10 on it to get the best out of it. I have followed a couple of guides but i have completely screwed this up!! After following the instructions (well thought i did anyway) i have gotten to the point where my phone is stuck in the boot loop (spinning circle thing).
I have tried following guides everywhere but i'm getting completely lost and getting more and more frustrated because i dont understand anything that is being explained.
So is there any way of getting my phone back to normal or some form of working condition because i would hate to have broken something i just bought within 7 hours of having it
Any help is much appreciated.
Click to expand...
Click to collapse
I guess you dint flash the boot.img..When you open the CM 10 zip file you will find the boot.img there...just extract it to a known location and flash the boot.img file and then install the rom as you did b4...that will solve the problem
Dont worry, nothing bad has happened to your phone and its just a extra step to be followed till v get s-off
:good:
kskendsup said:
I guess you dint flash the boot.img..When you open the CM 10 zip file you will find the boot.img there...just extract it to a known location and flash the boot.img file and then install the rom as you did b4...that will solve the problem
Dont worry, nothing bad has happened to your phone and its just a extra step to be followed till v get s-off
:good:
Click to expand...
Click to collapse
Do this 1st fast boot erase cache then flash the boot.IMG
Sent from my Xoom using xda app-developers app
---------- Post added at 10:36 PM ---------- Previous post was at 10:31 PM ----------
Just thought I'd share this what I copied from a good source what helped me when I started flashing my hox but I use Linux so I don't have a clue about any window issues
.) Open the .zip file and copy 'boot.img' to your fastboot folder. Or the folder you use
.) Turn off your phone and enter the bootloader (Hold the Volume Down and Power Keys while off).
) Select 'Fastboot' by pushing the Power Key.
.) Plug your phone into your computer using a USB cable.
.)Now go to your computer and open a command window inside the fastboot folder (Hold SHIFT + Right Click on any white-space).
.) Type 'fastboot devices.'
) Type 'fastboot erase cache' and push enter. This can fix problems with bootloops or bootfailures.
.) Type 'fastboot flash boot boot.img' and push enter. It should say 'OKAY' if successful.
.) On your phone, select 'HBOOT' using the Power Key and scroll down to 'Recovery' using the Volume Down Key. Push to Power Key again to select it.
Once in recovery you can navigate by tapping the screen or by using the Power and Volume Up/Down Keys.
.) Select 'wipe data/factory reset' and accept the warning screen.
) Now select 'advanced' and select 'wipe dalvik cache.'
) Select 'mounts and storage' and then 'mount USB storage.'
.) Copy the .zip file you downloaded (Don't unzip it!) onto the SD card of your phone.
.) Unmount USB Storage on your phone and navigate back to the Recovery Homescreen.
.) Now select 'install zip from sdcard' followed by 'choose zip from sdcard.'
.) Select the .zip file and let it install.
Sent from my Xoom using xda app-developers app
I actually love the both of you!!! My phone is working again
REALLY appreciate it! :laugh:
Thank you
Stuck in CM Boot Loop - please help!!
Hi guys,
I too am a bit of a noob in this. I had similar problems and then followed the instructions listed above. I saved the following files to my SD Card:
cm-10.2.0-RC1-endeavoru.zip
gapps-jb-20130813-signed.zip
First time round, after I rebooted the device, I managed to get through and set up my WiFi, log into my Google Account, but just as my Google account was registering and beginning to restore my apps, my phones screen suddenly reverted to the boot loop (spinning circle thing). Furthermore, the LED indicator is now steadily flashing in Red!
I am completely stuck here and any assistance this forum can provide will be much appreciated.
Thanks in advance!
someshj1577 said:
Hi guys,
I too am a bit of a noob in this. I had similar problems and then followed the instructions listed above. I saved the following files to my SD Card:
cm-10.2.0-RC1-endeavoru.zip
gapps-jb-20130813-signed.zip
First time round, after I rebooted the device, I managed to get through and set up my WiFi, log into my Google Account, but just as my Google account was registering and beginning to restore my apps, my phones screen suddenly reverted to the boot loop (spinning circle thing). Furthermore, the LED indicator is now steadily flashing in Red!
I am completely stuck here and any assistance this forum can provide will be much appreciated.
Thanks in advance!
Click to expand...
Click to collapse
Flash the boot.img!!!!
Thant said:
Flash the boot.img!!!!
Click to expand...
Click to collapse
Thanks Thant!
Just so you know, I first flashed the boot.img file (extracted it from the ROM package), then followed the steps in the post above.
This time round, the phone started up and I went through the initial set-up steps. Logged in to my Google account, everything seemed to work fine until I went to Play Store to check my apps. I briefly saw that my backed-up apps were downloading, then suddenly the phone went back to the CM boot screen (circular thing). That's how the phone has stayed.
What further do you guys advise?
Thanks.
someshj1577 said:
Thanks Thant!
Just so you know, I first flashed the boot.img file (extracted it from the ROM package), then followed the steps in the post above.
This time round, the phone started up and I went through the initial set-up steps. Logged in to my Google account, everything seemed to work fine until I went to Play Store to check my apps. I briefly saw that my backed-up apps were downloading, then suddenly the phone went back to the CM boot screen (circular thing). That's how the phone has stayed.
What further do you guys advise?
Thanks.
Click to expand...
Click to collapse
INSTRUCTIONS
First time installing CyanogenMod 10.2 to your HTC One X (GSM), or coming from another ROM:
Read the official wiki
Unlock your device via http://www.htcdev.com
Flash the latest official ClockworkMod-Recovery via Fastboot
Copy GApps and CM10.2 ZIPs to your SDCard
Boot into Recovery
Flash CM10.2 zip from SDCard
Flash GApps zip from SDCard
Flash the boot.img included in the CM10.2 zip via Fastboot
DO A DATA WIPE / FACTORY RESET
Reboot
Don't restore system data using Titanium Backup!
Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Thant said:
INSTRUCTIONS
First time installing CyanogenMod 10.2 to your HTC One X (GSM), or coming from another ROM:
Read the official wiki
Unlock your device via http://www.htcdev.com
Flash the latest official ClockworkMod-Recovery via Fastboot
Copy GApps and CM10.2 ZIPs to your SDCard
Boot into Recovery
Flash CM10.2 zip from SDCard
Flash GApps zip from SDCard
Flash the boot.img included in the CM10.2 zip via Fastboot
DO A DATA WIPE / FACTORY RESET
Reboot
Don't restore system data using Titanium Backup!
Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Click to expand...
Click to collapse
Thanks again, Thant! Your help is much appreciated.
Got the phone working with CM10.2, I played around with it for about 5 minutes, but not it has become unresponsive again. Pressing the power button to unlock the phone doesn't wake the screen, only the three soft buttons at the bottom light up, then nothing. If I leave the phone alone for a few minutes, it will wake up. I have since tried restarting the phone and it is working for the moment. I will report back if the screen hangs again.
Thanks again for your help.
someshj1577 said:
Thanks again, Thant! Your help is much appreciated.
Got the phone working with CM10.2, I played around with it for about 5 minutes, but not it has become unresponsive again. Pressing the power button to unlock the phone doesn't wake the screen, only the three soft buttons at the bottom light up, then nothing. If I leave the phone alone for a few minutes, it will wake up. I have since tried restarting the phone and it is working for the moment. I will report back if the screen hangs again.
Thanks again for your help.
Click to expand...
Click to collapse
Please try something for me.Turn on the screen and do a pressure between the right down side on main camera and display and see if the display flickering or do something strange.
Thant said:
Please try something for me.Turn on the screen and do a pressure between the right down side on main camera and display and see if the display flickering or do something strange.
Click to expand...
Click to collapse
Nope. Nothing. Although, I have noticed that the screen is taking a long time to wake up. When I press the pwer button, the screen should wake immediately, on the lock screen, but it is taking up to 2-3 minutes to wake. I have just now also noticed that when moving between screens or pulling the notification and app drawer, the display gets garbled and pixelated and screen flickers. It then sorts itself out.
I will try and capture a video of it happening and post it back here, if it helps.
someshj1577 said:
Nope. Nothing. Although, I have noticed that the screen is taking a long time to wake up. When I press the pwer button, the screen should wake immediately, on the lock screen, but it is taking up to 2-3 minutes to wake. I have just now also noticed that when moving between screens or pulling the notification and app drawer, the display gets garbled and pixelated and screen flickers. It then sorts itself out.
I will try and capture a video of it happening and post it back here, if it helps.
Click to expand...
Click to collapse
It is something like this
Thant said:
It is something like this
Click to expand...
Click to collapse
Yes, that's exactly what's going on. Although, I've been working with the device for a few hours now and I haven't seen the pixelated screen, but I have seen a delay in the screen waking to the lock screen.
Hardware..
Sent from my HTC One X using xda app-developers app
someshj1577 said:
Yes, that's exactly what's going on. Although, I've been working with the device for a few hours now and I haven't seen the pixelated screen, but I have seen a delay in the screen waking to the lock screen.
Click to expand...
Click to collapse
You have Black Screen of Dead sorry my friend you must to change the mainboard on the phone if you have warranty go back to full stock(stock rom and stock recovery), RELOCK the bootloader and send it for repair and hope they will repair free of charge if no warranty changing the mainboard will cost you some monеy. And I am right if you turn on the screen and you do pressure in the my point in previous post you will see the flickering and all the thing in this video. Sorry again
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
imhotap said:
Hardware..
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Right you are!
---------- Post added at 04:53 PM ---------- Previous post was at 04:51 PM ----------
Thant said:
You have Black Screen of Dead sorry my friend you must to change the mainboard on the phone if you have warranty go back to full stock(stock rom and stock recovery), RELOCK the bootloader and send it for repair and hope they will repair free of charge if no warranty changing the mainboard will cost you some monеy. And I am right if you turn on the screen and you do pressure in the my point in previous post you will see the flickering and all the thing in this video. Sorry again
Click to expand...
Click to collapse
Thank for your help! Glad to know guys like you are around!!
My phone's out of warranty, I'm afraid. I will carry on using it until it completely dies on me!!

TAB S T805 bricked while updating to LOLLIPOP 5.0.2

Hey everyone,
I just bricked my T805. I was following this guide:
[OFFICIAL] LOLLIPOP 5.0.2 /SM-T800/ SM-T805/ Firmwares T800XXU1BOCC / DOWNLOAD / ROOT
http://forum.xda-developers.com/galaxy-tab-s/general/samsung-lollipop-range-tab-s-t3021612
Installing Lollipop Firmware
Instructions:
1. Download the needed firmware from above.
2. Download Odin_3.10.0 from the attached file below
3. Open Odin, select AP and than select your firmware.
4. Make sure you have installed all samsung drivers
5. Shut down your Tab S.
6. Open download mode by holding volume down, home button and power button.
7. Connect it to your PC.
8. LEAVE EVERY THING AS IT IS IN ODIN, OTHERWISE THERE WILL BE A CATASTROPHE (If you select something wrong.)
9. When your tablet is connected, there will be a blue box in odin.
10. Hit start and wait
11. It will reboot and you will get the latest firmware from samsung.
Click to expand...
Click to collapse
So I was in Download mode, klicked on Start in ODIN.
After one minute, this is what followed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The Tab hangs in the Download mode screen...
USB connection does not work, PC is not recognizing the tab anymore.
Power off does not work, no chance to power down or reset the device (have to wail 'til battery is empty?)
Anyone knows what to do?
Thanks!
sheng1337 said:
Hey everyone,
I just bricked my T805. I was following this guide:
[OFFICIAL] LOLLIPOP 5.0.2 /SM-T800/ SM-T805/ Firmwares T800XXU1BOCC / DOWNLOAD / ROOT
http://forum.xda-developers.com/galaxy-tab-s/general/samsung-lollipop-range-tab-s-t3021612
So I was in Download mode, klicked on Start in ODIN.
After one minute, this is what followed:
The Tab hangs in the Download mode screen...
USB connection does not work, PC is not recognizing the tab anymore.
Power off does not work, no chance to power down or reset the device (have to wail 'til battery is empty?)
Anyone knows what to do?
Thanks!
Click to expand...
Click to collapse
You didn't read the WHOLE THREAD. If you had you wouldn't have had to make this unnecessary post.
Your image isn't showing.
californiarailroader said:
Your image isn't showing.
Click to expand...
Click to collapse
Use a browser.
Got ya, it must be a bug with Tapatalk. It looks like you did everything right, I followed those same instructions to flash my SM-T700 and I had no issues. I'm sorry about the brick, I've done it once and it's upsetting for sure.
Edit- Did you make sure you had all the drivers installed correctly and the PC detected and installed everything?
californiarailroader said:
Got ya, it must be a bug with Tapatalk. It looks like you did everything right, I followed those same instructions to flash my SM-T700 and I had no issues. I'm sorry about the brick, I've done it once and it's upsetting for sure.
Edit- Did you make sure you had all the drivers installed correctly and the PC detected and installed everything?
Click to expand...
Click to collapse
Hidden.img part of that file fails unless have a vodafone locked tablet. This was VERY well explained. Flash the latest T805 UAE firmware and it will be fine, no loss of data. READ BEFORE YOU FLASH!
lynxblaine said:
Hidden.img part of that file fails unless have a vodafone locked tablet. This was VERY well explained. Flash the latest T805 UAE firmware and it will be fine, no loss of data. READ BEFORE YOU FLASH!
Click to expand...
Click to collapse
Dang, I missed that part. Ok so, that is the deal, but how do I reboot the device? It's stuck in Download Mode since yesterday evening. Any Idea on this?
Restart with the download mode 3 button combo then flash the UAE firmware.
sheng1337 said:
Dang, I missed that part. Ok so, that is the deal, but how do I reboot the device? It's stuck in Download Mode since yesterday evening. Any Idea on this?
Click to expand...
Click to collapse
You're almost there, you have nothing more to do than boot to stock recovery then wipe the cache.
The tablet will then successfully boot to lollipop.
POWER +VOL DOWN + HOME to restart then immediately change to VOL UP whilst still holding POWER + HOME.
sheng1337 said:
Dang, I missed that part. Ok so, that is the deal, but how do I reboot the device? It's stuck in Download Mode since yesterday evening. Any Idea on this?
Click to expand...
Click to collapse
For reboot you can also press and hold a few seconds only 2 buttons HOME and VOL-
lynxblaine said:
Restart with the download mode 3 button combo then flash the UAE firmware.
Click to expand...
Click to collapse
Ok I finally managed to get into download mode again. So i'm in Odin Mode. But please, can you explain why I should flash the UAE version?
ashyx said:
You're almost there, you have nothing more to do than boot to stock recovery then wipe the cache.
The tablet will then successfully boot to lollipop.
POWER +VOL DOWN + HOME to restart then immediately change to VOL UP whilst still holding POWER + HOME.
Click to expand...
Click to collapse
I can't boot to stock recovery. I only managed to get into download mode. Recovery is not working.
UAE as it flashes nicely it's got the highest change list and it's clean - no bloat. I flashed it earlier today.
lynxblaine said:
UAE as it flashes nicely it's got the highest change list and it's clean - no bloat. I flashed it earlier today.
Click to expand...
Click to collapse
UAE is the country code for United Arabian Kingdoms, but I have a german device. Well it's not going to be worse than it is, so i will give it a try. Thanks, I will report back.
Sent from my Nexus 5 using XDA Free mobile app
sheng1337 said:
I can't boot to stock recovery. I only managed to get into download mode. Recovery is not working.
Click to expand...
Click to collapse
All you have to do is flash one.
I live in the UK, the firmware region makes little difference apart from that it can determine the bloatware you get. You will get offered the next OTA from the region you are in: but you can always manually flash any newer ROM.
Thank you very much all. I got it working, POWER+VOLDOWN to resrart, instantly HOME+VOLDOWN+POWER to switch to Download Mode. Connecting to PC, flashed UAE version with ODIN. TAB runs good now! Apps and Data were not cleared/wiped.
Thanks again!
Sent from my Nexus 5 using XDA Free mobile app

Rooted Elephone P8000 stucks at Boot Logo after OTA Update

Hi there,
The phone is rooted.
I've proceeded with the latest update today (~12mb size), don't remember the exact version.
It said it fixes some system bugs, etc.
After the update installed the phone won't load, stucks on the changing color logo.
Cannot access the recovery mode option in the boot menu (Vol+Power), says "no command", if press and hold Vol+ and Power again the phone restarts and enter the boot logo again.
Has anyone ideas how this can be fixed?
vagifn said:
Hi there,
The phone is rooted.
I've proceeded with the latest update today (~12mb size), don't remember the exact version.
It said it fixes some system bugs, etc.
After the update installed the phone won't load, stucks on the changing color logo.
Cannot access the recovery mode option in the boot menu (Vol+Power), says "no command", if press and hold Vol+ and Power again the phone restarts and enter the boot logo again.
Has anyone ideas how this can be fixed?
Click to expand...
Click to collapse
See http://forum.xda-developers.com/elephone-p8000/help/boot-loop-ota-upgrade-t3246203.
Post #16 describes how get into recovery from the 'no command' screen, and my post #12 describes how I managed to get it flashed using the SP Flashtool.
(Note my point no,5 - all I needed to do is press 'Download' first, THEN attach the powered off phone.)
Good luck!
kevvyboy said:
See http://forum.xda-developers.com/elephone-p8000/help/boot-loop-ota-upgrade-t3246203.
Post #16 describes how get into recovery from the 'no command' screen, and my post #12 describes how I managed to get it flashed using the SP Flashtool.
(Note my point no,5 - all I needed to do is press 'Download' first, THEN attach the powered off phone.)
Good luck!
Click to expand...
Click to collapse
Thanks a lot fot pointing this out.
Managed to get the recovery options menu.
However wiping the cache didn't help.
After doing the "root integrity check" got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
do you think this can be fixed w/o reflashing an entire rom?
Oooh. Brighter minds than mine might correct me, but I think the bootloop is only fixed with a ROM flash
kevvyboy said:
Oooh. Brighter minds than mine might correct me, but I think the bootloop is only fixed with a ROM flash
Click to expand...
Click to collapse
Sad... anyway would you please direct me to where I can download the flash tool and stock ROM? Thanks.
kevvyboy said:
Oooh. Brighter minds than mine might correct me, but I think the bootloop is only fixed with a ROM flash
Click to expand...
Click to collapse
Actually, what you need to do is format the data partition or write the empty data.img file over the data partition which in effect does the same thing. And the later one is also what happens when your download entire rom using sp flash.
pitrus- said:
Actually, what you need to do is format the data partition or write the empty data.img file over the data partition which in effect does the same thing. And the later one is also what happens when your download entire rom using sp flash.
Click to expand...
Click to collapse
I've proceeded with "wipe data/factory reset" option - no effect...or are we talking about different things?
vagifn said:
I've proceeded with "wipe data/factory reset" option - no effect...or are we talking about different things?
Click to expand...
Click to collapse
In that case you probably need to flash the system.img and maybe even the boot.img from the latest rom. Elephone really should stop sending out these broken OTAs...
pitrus- said:
In that case you probably need to flash the system.img and maybe even the boot.img from the latest rom. Elephone really should stop sending out these broken OTAs...
Click to expand...
Click to collapse
I believe the case is that my phone is rooted and this is not the Elephone team's fault...anyways thanks for trying to help me.
vagifn said:
I believe the case is that my phone is rooted and this is not the Elephone team's fault...anyways thanks for trying to help me.
Click to expand...
Click to collapse
You belive this b***** that feed you on official forum? OTA should work on any device software config.
ruonim said:
You belive this b***** that feed you on official forum? OTA should work on any device software config.
Click to expand...
Click to collapse
I didn't read official forum. However you do loose your warranty if device is rooted, thus the device manufacturer owes you nothing. OTA worked fine before I rooted my device.
Btw, I got my phone back to life by re-flashing the entire ROM, just in case.
Hello my friend
vagifn said:
Hi there,
The phone is rooted.
I've proceeded with the latest update today (~12mb size), don't remember the exact version.
It said it fixes some system bugs, etc.
After the update installed the phone won't load, stucks on the changing color logo.
Cannot access the recovery mode option in the boot menu (Vol+Power), says "no command", if press and hold Vol+ and Power again the phone restarts and enter the boot logo again.
Has anyone ideas how this can be fixed?
Click to expand...
Click to collapse
The only thing you need to do is reinstall the añl the system with spflashtool. Never and remember never you can update any android with a ota if you are a rooted user.
If you speak spanish you can search in the youtube channel AndroidMxL to ser how you can reinstall the original ROM on your android.
allianzcred said:
The only thing you need to do is reinstall the añl the system with spflashtool. Never and remember never you can update any android with a ota if you are a rooted user.
If you speak spanish you can search in the youtube channel AndroidMxL to ser how you can reinstall the original ROM on your android.
Click to expand...
Click to collapse
Already did, thanks. Will never combine Root and OTA together again

Requesting urgent help

Hello everyone
I was trying to do an OTA update for AOSP Extended custom rom on a Lenovo ZUK Z2 Plus phone from its then v6.2 to v6.6 and along the way encountered many problems and now my phone is now in an unusable state.
I'll state the issues I encountered in order:
-Do above mentioned OTA update for AOSP Extended. It downloads and shows it installed successfully but upon restart it refuses to boot the OS
-Stuck on that black screen with options for recovery. I think it is called fastboot screen? or perhaps bootloader screen. The one where you use volume keys to navigate.
-I chose Recovery option and it opened up TWRP. I clicked Install and selected my ROM manually but then was unable to install a newly downloaded AOSP due to an error #7
-I figure maybe updating TWRP to the latest version will help. I flash TWRP img and reboot.
-Upon reboot I find myself unable to even get back into recovery!.. the option to enter recovery exists but whenever I pick it it just restarts and throws me back to the fastload/bootloader black screen.
-I was stuck here for several hours before deciding to flash stock firmware via QFIL since fastboot was still working fine.
-I successfully flash stock firmware through QFIL using my computer. I reboot the phone and now a new issue:
I press the power button to turn my phone on but my phone screen briefly flashes a dimly lit black screen and then goes off, again flashes the black screen and goes off again. It keeps repeating this in a continuous unending loop.
I am literally out of ideas. I don't even want to get the stock rom anymore just want a usable phone again : (
I would greatly appreciate any help please.
Thank you for your time.
I wanted to post an update.
I was able to get out of this strange loop by holding power button and pressing volume up as soon as the led lit once and before the ZUK logo popped up.
Afterwards I did the Power+ Volume UP + Plug USB cable to get the qualcomm port thing and re-try flashing Stock firmware. Unfortunately the same problem after flashing, no errors in log, with the black screen being lit and then off again in loop. Could anyone tell me how to get to custom rom or even stock firmware from this position please.
The only thing you can do is QFIL stock rom. That should solve the problem. Try doing it correctly one more time and report with any type of errors.
Don't worry it'll be fine. Any type of software related problems can be solved just have to keep trying, who knows what solution may work!
the_harsh said:
The only thing you can do is QFIL stock rom. That should solve the problem. Try doing it correctly one more time and report with any type of errors.
Don't worry it'll be fine. Any type of software related problems can be solved just have to keep trying, who knows what solution may work!
Click to expand...
Click to collapse
Could you guide me to a specific stock rom I can use with QFIL method please?
I used a ' Lenovo_Zuk_Z2_Z2132_EN_OPEN_USER_Q01080.2_N_ZUI_2.5.104_ST_170418_QPST ' however now whenever I power my phone it takes me to this screen always:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Maky-313 said:
Could you guide me to a specific stock rom I can use with QFIL method please?
I used a ' Lenovo_Zuk_Z2_Z2132_EN_OPEN_USER_Q01080.2_N_ZUI_2.5.104_ST_170418_QPST ' however now whenever I power my phone it takes me to this screen always:
Click to expand...
Click to collapse
Flashing this ROM should solve the issue however flash again to confirm. I was in the same situation before but I don't remember exactly what I did.
Try pressing all three buttons (+- and power).
Maky-313 said:
Could you guide me to a specific stock rom I can use with QFIL method please?
I used a ' Lenovo_Zuk_Z2_Z2132_EN_OPEN_USER_Q01080.2_N_ZUI_2.5.104_ST_170418_QPST ' however now whenever I power my phone it takes me to this screen always:
Click to expand...
Click to collapse
okay this is strange....never encountered this screen before. Can you put your phone to EDL mode? If yes then try doing a QFIL any 3.5+ ZUI. It should solve the problem!
Although I've once successfully flashed ZUI 4.0.199, you can follow this guide for 3.5:
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/oreo-zuio3-5-099dev-z2-t3719682
the_harsh said:
okay this is strange....never encountered this screen before. Can you put your phone to EDL mode? If yes then try doing a QFIL any 3.5+ ZUI. It should solve the problem!
Although I've once successfully flashed ZUI 4.0.199, you can follow this guide for 3.5:
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/oreo-zuio3-5-099dev-z2-t3719682
Click to expand...
Click to collapse
I am currently downloading a Z2131_CN_OPEN_USER_Q00030.1_O_ZUI_3.5.389_ST_180525_qpst.zip for another thread. Is this the same as one of the ones in the thread linked by you? If not I'll abort.
Also, I previously had AOSP 6.2 which iirc was based on Android 9.0, do you feel perhaps me trying to flash older stock roms such as the earlier oreo(I think) based ones are causing issues? or is that not a problem flashing older android version based firmware/roms.
Maky-313 said:
I am currently downloading a Z2131_CN_OPEN_USER_Q00030.1_O_ZUI_3.5.389_ST_180525_qpst.zip for another thread. Is this the same as one of the ones in the thread linked by you? If not I'll abort.
Also, I previously had AOSP 6.2 which iirc was based on Android 9.0, do you feel perhaps me trying to flash older stock roms such as the earlier oreo(I think) based ones are causing issues? or is that not a problem flashing older android version based firmware/roms.
Click to expand...
Click to collapse
well, i guess you've downloaded and tried it as it's been more than an hour now. also if you had AEX (not AOSP I presume) 6.2 then you must have flashed 3.5 to update the firmware, so flashing older one can be a problem. Is the new one working?
the_harsh said:
well, i guess you've downloaded and tried it as it's been more than an hour now. also if you had AEX (not AOSP I presume) 6.2 then you must have flashed 3.5 to update the firmware, so flashing older one can be a problem. Is the new one working?
Click to expand...
Click to collapse
I went ahead and downloaded the Zui.3.5.389.qpst from your earlier linked thread. I used QFIL just now to flash it, unfortunately the phone still won't boot.
When I press the power button the white LED turns on for a second and then goes off after which is just a Solid black screen throughout. Doesn't make difference if I press the power button and let go or hold the power button down the same behaviour each time.
This was also the behaviour on earlier flashes of 1_M_ZUI_2.0.093_ST_160811_qpst & 2_N_ZUI_2.5.104_ST_170418_QPST : (
Maky-313 said:
I went ahead and downloaded the Zui.3.5.389.qpst from your earlier linked thread. I used QFIL just now to flash it, unfortunately the phone still won't boot.
When I press the power button the white LED turns on for a second and then goes off after which is just a Solid black screen throughout. Doesn't make difference if I press the power button and let go or hold the power button down the same behaviour each time.
This was also the behaviour on earlier flashes of 1_M_ZUI_2.0.093_ST_160811_qpst & 2_N_ZUI_2.5.104_ST_170418_QPST : (
Click to expand...
Click to collapse
are you sure your phone is being recognized in PC correctly and the flashing stock ROM don't endup in any error?
the_harsh said:
are you sure your phone is being recognized in PC correctly and the flashing stock ROM don't endup in any error?
Click to expand...
Click to collapse
I think its recognised as the correct qualcomm device under ports in device manager but I will take a screenshot for you so you can have a look.
and later today I'll reflash and save a log this time for the same 3.5 ROM and share that as well.
Samirmathakiya said:
Flashing this ROM should solve the issue however flash again to confirm. I was in the same situation before but I don't remember exactly what I did.
Try pressing all three buttons (+- and power).
Click to expand...
Click to collapse
the_harsh said:
are you sure your phone is being recognized in PC correctly and the flashing stock ROM don't endup in any error?
Click to expand...
Click to collapse
guys it worked! I just decided to leave it plugged into the charger for a while and left.
After coming back I long-pressed the power button to make sure it was powered off before attempting to use the key combination to put it in EDL mode and I guess I pressed it too short or let go of the power perhaps but it booted right into the OS : )
I feel now that earlier perhaps the phone didn't have enough charge to go past the initial zuk booting logo perhaps? I did not charge it since yesterday and would only be plugged into the usb for edl attempts, perhaps that was just enough to get flashing but not enough to boot the phone. I now wonder if previous flashing attempts were indeed successful and I just didn't have the battery to get it past the initial boot logo screen : S...
One last request please : )
I would like you guys to advise a custom rom for me please. I am looking for a stock android experience wherein the UI is very smooth and slick, I would also like to have a long battery life please if possible. I don't play games etc. so 3d performance or processing power is not a priority.
Thank you.
Maky-313 said:
guys it worked! I just decided to leave it plugged into the charger for a while and left.
After coming back I long-pressed the power button to make sure it was powered off before attempting to use the key combination to put it in EDL mode and I guess I pressed it too short or let go of the power perhaps but it booted right into the OS : )
I feel now that earlier perhaps the phone didn't have enough charge to go past the initial zuk booting logo perhaps? I did not charge it since yesterday and would only be plugged into the usb for edl attempts, perhaps that was just enough to get flashing but not enough to boot the phone. I now wonder if previous flashing attempts were indeed successful and I just didn't have the battery to get it past the initial boot logo screen : S...
One last request please : )
I would like you guys to advise a custom rom for me please. I am looking for a stock android experience wherein the UI is very smooth and slick, I would also like to have a long battery life please if possible. I don't play games etc. so 3d performance or processing power is not a priority.
Thank you.
Click to expand...
Click to collapse
Stick with official lineage os now
https://download.lineageos.org/z2_plus
Maky-313 said:
guys it worked! I just decided to leave it plugged into the charger for a while and left.
After coming back I long-pressed the power button to make sure it was powered off before attempting to use the key combination to put it in EDL mode and I guess I pressed it too short or let go of the power perhaps but it booted right into the OS : )
I feel now that earlier perhaps the phone didn't have enough charge to go past the initial zuk booting logo perhaps? I did not charge it since yesterday and would only be plugged into the usb for edl attempts, perhaps that was just enough to get flashing but not enough to boot the phone. I now wonder if previous flashing attempts were indeed successful and I just didn't have the battery to get it past the initial boot logo screen : S...
One last request please : )
I would like you guys to advise a custom rom for me please. I am looking for a stock android experience wherein the UI is very smooth and slick, I would also like to have a long battery life please if possible. I don't play games etc. so 3d performance or processing power is not a priority.
Thank you.
Click to expand...
Click to collapse
Derp caf pie is also very good..
On it for 3 days now and quite stable rom.. definitely recommend
congratulations on getting it done! as a thankyou gesture you can give me party in Starbucks ? (JK).
For Custom ROM
If you want something with customizations I'd say go with AOSiP pie. The best and latest I've used.
But if you want to stick more to the stock Android side you should go with Lineage pie. It's the best in business.
the_harsh said:
congratulations on getting it done! as a thankyou gesture you can give me party in Starbucks (JK).
For Custom ROM
If you want something with customizations I'd say go with AOSiP pie. The best and latest I've used.
But if you want to stick more to the stock Android side you should go with Lineage pie. It's the best in business.
Click to expand...
Click to collapse
yup yup I went ahead with the Lineage OS 16 as it seemed to be very popular. So far so good.
Thank you and everyone else for your help. God bless : )

Categories

Resources