i have problem after flashing wrong recovery img to to lg p769 ,the phone stock with lg logo with Security Error.
i try to flash V20D_00.kdz with no luck.it was abig problem ,and i try alot of ways you name it ,and search the net with no luck .untill i see post wasn't clear .So i put it togther to be an eazy way to fix LG SECURITY ERROR
you need :
1-fastboot zip file for ( l9 p760 p765 p768 p769 )from here http://forum.xda-developers.com/showthread.php?p=41768774 thanks to Lelus
unzip it and move to C:/ direct
2- this script below and the ALL (3) img from here http://forum.xda-developers.com/showthread.php?p=43642515&highlight=lelus+batch+script#post43642515 thanks to kuma82
move the (3) img's to bin folder inside C:/fastboot/bin
fastboot devices
fastboot erase u-boot
fastboot erase boot
fastboot erase recovery
fastboot flash u-boot 2u-ice.img
fastboot flash boot 3boot-ice.img
fastboot flash recovery 4recovery-ice.img
3-KDZ_FW_UPD_EN.zip and shttps.zip (if you dont have them) from here http://forum.xda-developers.com/showthread.php?p=36351786 thanks to cmahendra
4- you KDZ or ROM from here http://forum.xda-developers.com/showthread.php?t=2107971
instuction
1- put you phone in fastboot mode ,follow this post http://forum.xda-developers.com/showpost.php?p=44578108&postcount=34 thanks to kuma82 for the images
2-Run cmd (run as administrator) and drag the bin foler to cmd directory OR type cd C:\fastboot\bin
3-copy and past the script in # 2 one at the time .then toen off the phone
4-hold the Volume UP and plug the USB to the phone to be in Software Upgrade Mode.
you can follow this post http://forum.xda-developers.com/showthread.php?p=36351786 thanks to cmahendra,
you should have you phone back unbricked
good luck
I have been pulling my hair out for 3 days trying to un-soft brick my phone. Tried everything and kept getting stuck. Your write up and links to the other posts made everything super easy. First try today and I'm back up and running thanks to you. 20 thumbs up.
The issue i am having is keeping the LG P2 or anything in device manager stable without it consantly reloading.
I did manage to get to S/W upgrading once (but didnt have the other steps installed/finished yet.) I think i did it by eventually doing step 5 (after all the step 1 stuff) on lelus fastboot.
Im hoping i cant just jump right off there (IF i can get it to get to s/w again) as im guessing all s/w upgrade screens are the same point.
Crossing my fingers that i can figure out how to make all this work! Stupide security lock
It works!
Holy crap this works!
I retried everything fresh on another pc, everything worked on first try. Sorta, i mean i did kinda forget how to get into S/W upgrade mode, but i got there on the second try.
Anyways, 1000000 million thank yous for this write up! Now i just need to remember how to root this thing!
@fox12345
Thanks for taking the time to provided some instructions. I've been meaning to do so but been busy with other stuff.
I don't like asking for thanks, but sometimes I do. If it's not much of a problem, hit the thanks button on my posts provided in your thread.
Sent from my LGMS769 using XDA Premium 4 mobile app
Help
I am having the same problems. I did you method and the only change is now the "Security Error" is gone but phone still wont boot or enter recovery or S/W update mode. When this all started I had stock GB on it. I downloaded a version of JB V20F_00 that supposedly had an unlocked bootloader. I made it through root, installing CWM as TWRP wouldn't install, and flashed a version of CM 11 for it. When it rebooted it had the security error. I have completed your steps but now cannot enter recovery or S/W Upgrade mode. I have tried holding the Vol Up key and inserting the cable without the battery, holding the Vol Down and plugging it in sans battery, holding both Vol buttons and plugging it in sans battery, and all the same steps with the battery connected. No luck. Any help you could give would be much appreciated
disinfectantrum said:
I am having the same problems. I did you method and the only change is now the "Security Error" is gone but phone still wont boot or enter recovery or S/W update mode. When this all started I had stock GB on it. I downloaded a version of JB V20F_00 that supposedly had an unlocked bootloader. I made it through root, installing CWM as TWRP wouldn't install, and flashed a version of CM 11 for it. When it rebooted it had the security error. I have completed your steps but now cannot enter recovery or S/W Upgrade mode. I have tried holding the Vol Up key and inserting the cable without the battery, holding the Vol Down and plugging it in sans battery, holding both Vol buttons and plugging it in sans battery, and all the same steps with the battery connected. No luck. Any help you could give would be much appreciated
Click to expand...
Click to collapse
If your phone appears dead, then something messed up with fastboot. Run fastboot again and flash an ice cream x & u (select the option for your device).
Sent from my LGMS769 using XDA Premium 4 mobile app
kuma82 said:
If your phone appears dead, then something messed up with fastboot. Run fastboot again and flash an ice cream x & u (select the option for your device).
Sent from my LGMS769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks much for the reply. Im pretty sure it was actually a driver conflict of some sort as when I installed the same exact everything in another computer and reattempted to enter sw mode it worked perfectly. still got hung at 15% but closing all programs, running ccleaner, and rebooting allowed me to flash V20D_00. All is good now.
you guys are amazing
wow...was just to give up on my l9 w/security error as a casualty of my compulsive need to jack around with my phones and I find this. I had rooted and tried to flash CWM when everything went wrong. I had been deep into cmahendra's thread but my phone was never recognized...I was missing the fastboot/flashing step. Once I flashed the .img files cmahendra's awesome method went off without a hitch.
OK so I feel like I can get it back to stock if I screw up so I'm gonna go root it and try to flash a custom rom (bookmarking this thread...fairly certain I'll be back lol)
THANK YOU FOR THIS THREAD AND ALL YOUR WORK!!
kmonagle said:
wow...was just to give up on my l9 w/security error as a casualty of my compulsive need to jack around with my phones and I find this. I had rooted and tried to flash CWM when everything went wrong. I had been deep into cmahendra's thread but my phone was never recognized...I was missing the fastboot/flashing step. Once I flashed the .img files cmahendra's awesome method went off without a hitch.
OK so I feel like I can get it back to stock if I screw up so I'm gonna go root it and try to flash a custom rom (bookmarking this thread...fairly certain I'll be back lol)
THANK YOU FOR THIS THREAD AND ALL YOUR WORK!!
Click to expand...
Click to collapse
If your bootloader is locked you're gonna end up with a mess to straighten out. It can be fixed tho. Bootloader must be unlocked to flash custom recovery and/or ROM.
I'm currently trying to go through the steps. I am on the part to run commands for the img files but i get this error "error: cannot load '2u-ice.img' "
Am i doing something wrong?
screen not working
fox12345 said:
i have problem after flashing wrong recovery img to to lg p769 ,the phone stock with lg logo with Security Error.
i try to flash V20D_00.kdz with no luck.it was abig problem ,and i try alot of ways you name it ,and search the net with no luck .untill i see post wasn't clear .So i put it togther to be an eazy way to fix LG SECURITY ERROR
you need :
1-fastboot zip file for ( l9 p760 p765 p768 p769 )from here http://forum.xda-developers.com/showthread.php?p=41768774 thanks to Lelus
unzip it and move to C:/ direct
2- this script below and the ALL (3) img from here http://forum.xda-developers.com/showthread.php?p=43642515&highlight=lelus+batch+script#post43642515 thanks to kuma82
move the (3) img's to bin folder inside C:/fastboot/bin
fastboot devices
fastboot erase u-boot
fastboot erase boot
fastboot erase recovery
fastboot flash u-boot 2u-ice.img
fastboot flash boot 3boot-ice.img
fastboot flash recovery 4recovery-ice.img
3-KDZ_FW_UPD_EN.zip and shttps.zip (if you dont have them) from here http://forum.xda-developers.com/showthread.php?p=36351786 thanks to cmahendra
4- you KDZ or ROM from here http://forum.xda-developers.com/showthread.php?t=2107971
instuction
1- put you phone in fastboot mode ,follow this post http://forum.xda-developers.com/showpost.php?p=44578108&postcount=34 thanks to kuma82 for the images
2-Run cmd (run as administrator) and drag the bin foler to cmd directory OR type cd C:\fastboot\bin
3-copy and past the script in # 2 one at the time .then toen off the phone
4-hold the Volume UP and plug the USB to the phone to be in Software Upgrade Mode.
you can follow this post http://forum.xda-developers.com/showthread.php?p=36351786 thanks to cmahendra,
you should have you phone back unbricked
good luck
Click to expand...
Click to collapse
i did the fastboot, now it doesnt show security error, actually its not showing anything on my phone screen , update went till 50% and then says phone not connected. Im stuck.
what should i do now?
Huh??
phonecow said:
The issue i am having is keeping the LG P2 or anything in device manager stable without it consantly reloading.
I did manage to get to S/W upgrading once (but didnt have the other steps installed/finished yet.) I think i did it by eventually doing step 5 (after all the step 1 stuff) on lelus fastboot.
Im hoping i cant just jump right off there (IF i can get it to get to s/w again) as im guessing all s/w upgrade screens are the same point.
Crossing my fingers that i can figure out how to make all this work! Stupide security lock
Click to expand...
Click to collapse
I get an error cannot load ' '
swaggyp said:
I get an error cannot load ' '
Click to expand...
Click to collapse
i now be sercurity error too i find out to use lg support tool, but when i chose upgrade recovery this soft ware said that i have to conect phone to PC (but it conected and S/W mode, i also installed lastest driver and run with window 8) so what i have to do. I also read fastboot way but still cant instal usb_drv_windows any advise for me, thanks guys:crying:
it is still loading, yet thank you
fox12345 said:
i have problem after flashing wrong recovery img to to lg p769 ,the phone stock with lg logo with Security Error.
i try to flash V20D_00.kdz with no luck.it was abig problem ,and i try alot of ways you name it ,and search the net with no luck .untill i see post wasn't clear .So i put it togther to be an eazy way to fix LG SECURITY ERROR
you need :
1-fastboot zip file for ( l9 p760 p765 p768 p769 )from here http://forum.xda-developers.com/showthread.php?p=41768774 thanks to Lelus
unzip it and move to C:/ direct
2- this script below and the ALL (3) img from here http://forum.xda-developers.com/showthread.php?p=43642515&highlight=lelus+batch+script#post43642515 thanks to kuma82
move the (3) img's to bin folder inside C:/fastboot/bin
fastboot devices
fastboot erase u-boot
fastboot erase boot
fastboot erase recovery
fastboot flash u-boot 2u-ice.img
fastboot flash boot 3boot-ice.img
fastboot flash recovery 4recovery-ice.img
3-KDZ_FW_UPD_EN.zip and shttps.zip (if you dont have them) from here http://forum.xda-developers.com/showthread.php?p=36351786 thanks to cmahendra
.......good luck
Click to expand...
Click to collapse
Thanks for putting this guide up, I was stuck at the point where the LG Mobile Phone Software, would say that my device is not connected with USB. But I know it was because I had it all connected, it showed up in the device manger and was recognized by fastboot. I guess I just didn't have the right images to be compatible with flashed onto the device. Thanks to you putting all of this together, it finally worked again. Thanks a lot life saver!!!!!!!!!!!
Undesired lines in LG optimus L9 P765
I opted this method to unbrick because i was getting the same security error. And successfully installed all the 3 images. But it was after installing these the real problem came in. Now i could enter the bootloader but it appeared to be a set of multi colored lines. And when i tried to replace the installed recovery img with CWM img, the security error problem again came in. I am trapped in a situation that i have to get access somehow to CWM or any alternative. Can someone suggest me some good alternative for lg p765? or is there any work around for this?
Hello
I cant do
4-hold the Volume UP and plug the USB to the phone to be in Software Upgrade Mode.
because when I do it, my phone give me Security Error again !
How to solve it?
This is what happens to me:
Code:
ECHO está desativado.
Plug USB cable
wait 4 seconds and put battery back in.
waiting for OMAP44xx device...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
reading ASIC ID
usb_write 4
usb_read 81
[*] read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x4
Checksum Subblock: 0x15
CHIP: 4430
IDEN: fcf149ef997dfa51964b1dc43066037420a15e2a
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74795e9516194c0ea6412fdcb7f6
CRC0: 9c669ad9
CRC1: 682adccf
sending 2ndstage to target... f0030002
usb_write 4
usb_write 4
wait 5-lelelel...
[*] msg size = 4
usb_write 21552
[*] data size = 21552
usb_close
Reopen usb...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 246272
usb_write 4
usb_write 246272
** Done **
Microsoft Windows [versão 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Todos os direitos reservados.
C:\fastboot\yours>fastboot erase u-boot
< waiting for device >
^C
C:\fastboot\yours>fastboot erase boot
< waiting for device >
^C
C:\fastboot\yours>fastboot erase recovery
< waiting for device >
^C
C:\fastboot\yours>fastboot flash u-boot 2u-ice.img
error: cannot load '2u-ice.img'
C:\fastboot\yours>fastboot flash boot 3boot-ice.img
error: cannot load '3boot-ice.img'
C:\fastboot\yours>fastboot flash recovery 4recovery-ice.img
error: cannot load '4recovery-ice.img'
C:\fastboot\yours>
Am I doing something wrong?
Would there be a way without having to connect it to the pc? PC keeps losing connection, and doesn't recognize the device. I installed the OMAP drivers manually, but still it's not recognized. Could I try something from SD card maybe? Or is it time to throw it away?
Lg P760 after this procedure phone is compleatly dead.
C:\fastboot\bin>fastboot devices
016361571101D00E fastboot
C:\fastboot\bin>fastboot erase u-boot
erasing 'u-boot'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\fastboot\bin>fastboot erase boot
erasing 'boot'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\fastboot\bin>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\fastboot\bin>fastboot flash u-boot 2u-ice.img
sending 'u-boot' (1024 KB)...
OKAY [ 0.531s]
writing 'u-boot'...
OKAY [ 2.813s]
finished. total time: 3.344s
C:\fastboot\bin>fastboot flash boot 3boot-ice.img
sending 'boot' (6656 KB)...
OKAY [ 3.422s]
writing 'boot'...
OKAY [ 2.813s]
finished. total time: 6.234s
C:\fastboot\bin>fastboot flash recovery 4recovery-ice.img
sending 'recovery' (7680 KB)...
OKAY [ 3.938s]
writing 'recovery'...
OKAY [ 2.828s]
finished. total time: 6.766s
C:\fastboot\bin>
---------- Post added at 05:16 PM ---------- Previous post was at 04:57 PM ----------
Any help for unbrick?
Related
After I rooted my phone with LGPwn, I was attempting to set partitions on my sd card so that I would be able to use Link2SD. However, after I partitioned my phone, link2sd did not recognize my second partition, saying that it wasn't mounted, so I decided to reboot. After my phone shut off, It never turned back on. I have tried home, vol down, power, taken out battery, etc. When it is plugged into my pc, the computer seems to recognize it for a few seconds, and then disconnects. How do I fix this?
Have the same problem. Please HELP !
1pan1 said:
After I rooted my phone with LGPwn, I was attempting to set partitions on my sd card so that I would be able to use Link2SD. However, after I partitioned my phone, link2sd did not recognize my second partition, saying that it wasn't mounted, so I decided to reboot. After my phone shut off, It never turned back on. I have tried home, vol down, power, taken out battery, etc. When it is plugged into my pc, the computer seems to recognize it for a few seconds, and then disconnects. How do I fix this?
Click to expand...
Click to collapse
I have the exact same problem. Was using an app to create an ext2 partittion on my SD card, to use Link2sd. Ended up formating my phone. Now it wont do anything, it does not turn on in any way. My computer recognizes the phone when I connect it ( had to install some drivers). Im able to boot into fastboot mode. Now my question is how do i fix my partions. I have tried the following comands and this is what I get.
C:\fastboot\yours>fastboot erase system
erasing 'system'...
OKAY [ 0.173s]
finished. total time: 0.176s
C:\fastboot\yours>fastboot erase recovery
erasing 'recovery'...
FAILED (remote: : partition doesn't exist)
finished. total time: 0.007s
C:\fastboot\yours>fastboot erase boot
erasing 'boot'...
FAILED (remote: : partition doesn't exist)
finished. total time: 0.011s
C:\fastboot\yours>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.289s]
finished. total time: 0.292s
C:\fastboot\yours>fastboot erase splash
erasing 'splash'...
FAILED (remote: : partition doesn't exist)
finished. total time: 0.007s
C:\fastboot\yours>fastboot erase cache
erasing 'cache'...
OKAY [ 0.127s]
finished. total time: 0.130s
I guess my question is, what are the command to reformat and fix my partition . Please Help, This is my first brick.
Simply try to restore it through LG official tool :
http://forum.xda-developers.com/showpost.php?p=40423549&postcount=2
OperationNT said:
Simply try to restore it through LG official tool :
http://forum.xda-developers.com/showpost.php?p=40423549&postcount=2
Click to expand...
Click to collapse
I would.... but the thing is that to use the LG Software you need to put the phone in " S/W mode" and like I said before the phone does not turn on in any way (not even in S/W mode) because i formated the partitions. All I'm able to do is put on the phone in fastboot mode (the screen with the inverted LG logo, that says fastboot v5.0 on the top).
Thank for the suggestion though.
Are you sure ?
For example, if you remove the battery, then plug your phone in your computer USB without battery and finally maintain the Vol+ button while it's plugged, the device doesn't turn on in "S/W Upgrade" ?
I always thought "S/W Upgrade" mode was a very low level feature but maybe I am wrong.
OperationNT said:
Are you sure ?
For example, if you remove the battery, then plug your phone in your computer USB without battery and finally maintain the Vol+ button while it's plugged, the device doesn't turn on in "S/W Upgrade" ?
I always thought "S/W Upgrade" mode was a very low level feature but maybe I am wrong.
Click to expand...
Click to collapse
Nope, already tried it. I think I formatted the partition that had the img file for S/W Update .......
The only solution I have found is to boot into fastboot mode... All I need is the command or way to reformat or fix the partitions using fastboot.
Bump .. Found I guy who had the same problem and created a guide on how to fix it, here is a link http://forum.cyanogenmod.com/topic/71825-hard-brick-to-hell-and-back-guide-to-recovery/.... Now if we can just find a way to apply the same method to our LG L9, then maybe we could fix the phone.
I hope you can find a solution to your issue. But, while I was reading the solution for E730, I see one issue : when you extract KDZ files from P760 firmware, you only get ".bin" and ".fls" files.
I don't know how those files can be extracted again to get the real final files. I saw this issue with V20I_00.kdz, maybe you could try an older version such as V10A_00.kdz.
Good luck !
EDIT : Did you try this solution ?
http://forum.xda-developers.com/showthread.php?t=2612356
Try flashing ics x and u in fastboot. See if you're able to get a boot to s/w upgrade mode.
I downloaded a stock firmware (V20a D618) and at installation via LG Flash Tool, the USB cable was left with bad contact and gave installation error; After that when I turn on my phone it is only showing the logo of LG and the upper right corner appears:
"[710] fastboot_init()
[810] USB init ept @ 0x1001d000
[830] udc_start()"
I can't enter in download mode, fastboot, recovery, bootloader, nothing...
Any solution???? :crying:
(sorry to my english.)
You need to reflash your system.
But first, try to flash proper boot.img for your device.
Search on XDA.
If you done it correctly, your phone boots up straight to the bootloader.
Try also this trick :
0. Turn off your phone (dOH!), take out battery pack for about 20sec and re-insert battery.
1. Hold VOLUME DOWN and POWER BUTTON.
2.After LG logo, right away, LET DOWN POWER BUTTON and PRESS IT AGAIN AND HOLD.
3. Maybe that will put into download mode.
(It should'nt because its for factory reset, but who knows?)
SuperBadGateway502 said:
You need to reflash your system.
But first, try to flash proper boot.img for your device.
Search on XDA.
If you done it correctly, your phone boots up straight to the bootloader.
Try also this trick :
0. Turn off your phone (dOH!), take out battery pack for about 20sec and re-insert battery.
1. Hold VOLUME DOWN and POWER BUTTON.
2.After LG logo, right away, LET DOWN POWER BUTTON and PRESS IT AGAIN AND HOLD.
3. Maybe that will put into download mode.
(It should'nt because its for factory reset, but who knows?)
Click to expand...
Click to collapse
I tried send the command "fastboot flash boot boot.img" but I always have message
"C:\Users\David\Downloads\LG>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (15872 KB)...
OKAY [ 0.703s]
writing 'boot'...
FAILED (remote: unknown command)
finished. total time: 0.719s"
however when I run the command, the phone receives, but it does not know how to execute, how do I make him accept commands???
(sorry to my english)
bieldobaixo said:
I tried send the command "fastboot flash boot boot.img" but I always have message
"C:\Users\David\Downloads\LG>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (15872 KB)...
OKAY [ 0.703s]
writing 'boot'...
FAILED (remote: unknown command)
finished. total time: 0.719s"
however when I run the command, the phone receives, but it does not know how to execute, how do I make him accept commands???
(sorry to my english)
Click to expand...
Click to collapse
I don't know why your phone doesn't accept the boot.img (maybe try another boot.img ?).
But in case that won't work, you can always try to enter download mode by this method :
http://forum.xda-developers.com/g2-mini/general/guide-unbrick-bricked-wrong-aboot-img-t3128896
In summary : let your battery goes 0%, then try to power the phone, it won't and will show you the low battery icon : at this moment, press and hold the volume low button, and connect it to you computer, the phone should enter in download mode. Then you can flash a .kdz .
It worked for me when a realy bricked my phone and cannot acces either the recovery or fastboot .
Please help - Vodafone gives customers the tablets, but unfortunately it can not make phone calls. Apparently it is consistent with Alcatel mentioned above. I need to get the best official ROM ....
Vodafone Smart Tab 4G ROMs and rooting
stir62 said:
Please help - Vodafone gives customers the tablets, but unfortunately it can not make phone calls. Apparently it is consistent with Alcatel mentioned above. I need to get the best official ROM ....
Click to expand...
Click to collapse
See this:
http://forum.xda-developers.com/general/rooting-roms/vodafone-smart-tab-4g-t2992870/page5
First download and decompress:
SmartTab4G_Recovery_KK_benjaminwan_EN.zip
switch on the smart tab 4g
and in command line in a terminal type:
adb reboot bootloader
fastboot -i 0x1bbb oem unlock
fastboot -i 0x1bbb boot cwm.img
wait a little and then you will see the CWM screen and then install the cm-11-20150714-M12-pop8lte.zip file which must be copied on the microSD TF card you inserted in the tablet. When the flashing is over, reboot and you're ready to go.
This ROM is pre-rooted. No need to root after.
Good luck.
Here is the full list of ROMs and tools for the Vodafone Smart Tab 4G
This should be unzipped on the PC:
http://www.mediafire.com/download/3mr2zgx27x2arst/SmartTab4G_Recovery_KK_benjaminwan.zip
And the following are all pre-rooted ROMs that are copied on the microSD card we insert in the tablet:
http://www.mediafire.com/download/hdra4r5j48lbl7j/cm-11-20150714-M12-pop8lte.zip
http://www.mediafire.com/download/t29mkypa6poloc4/LS-KK-KTU84Q-2015-07-17-pop8lte.zip
http://www.mediafire.com/download/19e3za4l223rhkk/aokp_pop8lte_kitkat_unofficial_2015-07-17.zip
http://www.mediafire.com/download/1y2o3wywvu7rp4a/CARBON-KK-KTU84Q-20150716-BJW-pop8lte.zip
http://www.mediafire.com/download/57pitjl3yezm33z/FIUI_for_pop8lte_beta_2.28.0.zip
http://www.mediafire.com/download/2r119sl8kpaoc24/IUNI-pop8lte-BetaV3.0.05-201504130001.zip
http://www.mediafire.com/download/lgckk71dpdfvnp5/MIUI6_pop8lte_BJW_KitKat_15.07.26.zip
http://www.mediafire.com/download/c25p2oj01wf8wlo/MK44.4-pop8lte-20150715-KTU84Q-bjw.zip
the following are the Google Apps (GAPPS) packages that are also copied on the microSD card we insert in the tablet:
http://www.mediafire.com/download/aem9d5c6xsmj96p/pa_gapps-modular-nano-4.4.4-20150410-signed.zip
http://www.mediafire.com/download/qmico727b57v2qj/pa_gapps-modular-pico-4.4.4-20150410-signed.zip
Finally, this is the Vodafone stock ROM:
http://www.mediafire.com/download/dgc6655bjf05kje/vodafone-smart-tab4g-stock-full.zip
enjoy!
tried to install stock ROM and cm-11-20150714-M12-pop8lte ROM with Android system recovery but after verifing update package had this message :
failed to verify whole-file signature
signature verification failed
installation aborted
what is the mistake?
my Tab is every time on booting logo Vodafone
vodafone smart tab 4g
cratilo said:
tried to install stock ROM and cm-11-20150714-M12-pop8lte ROM with Android system recovery but after verifing update package had this message :
failed to verify whole-file signature
signature verification failed
installation aborted
what is the mistake?
my Tab is every time on booting logo Vodafone
Click to expand...
Click to collapse
Excuse me, what Android system recovery do you mean? The system recovery menu that the vodafone smart tab 4g has by default?
I didn't mention this recovery method in my writing. Other method I explained. The CWM recovery method as follows:
First download and decompress:
SmartTab4G_Recovery_KK_benjaminwan_EN.zip
switch on the smart tab 4g and connect it via USB to your PC. USB debugging should be turned ON!
and in command line in a terminal type:
adb reboot bootloader
fastboot -i 0x1bbb oem unlock
fastboot -i 0x1bbb boot cwm.img
wait a little and then you will see the CWM screen and then install the cm-11-20150714-M12-pop8lte.zip file which must be copied on the microSD TF card you inserted in the tablet. When the flashing is over, reboot and you're ready to go.
---------- Post added at 04:59 PM ---------- Previous post was at 04:42 PM ----------
cratilo said:
tried to install stock ROM and cm-11-20150714-M12-pop8lte ROM with Android system recovery but after verifing update package had this message :
failed to verify whole-file signature
signature verification failed
installation aborted
what is the mistake?
my Tab is every time on booting logo Vodafone
Click to expand...
Click to collapse
Now you need to go into the bootloader mode on the tablet.
So,
1. Switch it OFF
2. Press and hold the volume DOWN button together with the power ON button and keep them pressed for 5 seconds until you see on the tablet screen the black screen with the writing "POWERED BY android" in white at the bottom. You are now in bootloader mode.
3. Connect the tablet via USB to your PC
4. Download and decompress: SmartTab4G_Recovery_KK_benjaminwan_EN.zip
5. In command line in a terminal window on your PC type:
fastboot -i 0x1bbb oem unlock
fastboot -i 0x1bbb boot cwm.img
wait a little and then you will see the CWM screen and then install the cm-11-20150714-M12-pop8lte.zip or any other ROM file which must be copied on the microSD TF card you inserted in the tablet. The Google APPS (nano and pico) zip files should also be present on the TF MicroSD. After installing the ROM file from zip on the SD card we need install one of the GAPPS files. I personally installed the pico to have more space on the /system partition.
[/COLOR]
Now you need to go into the bootloader mode on the tablet.
So,
1. Switch it OFF
2. Press and hold the volume DOWN button together with the power ON button and keep them pressed for 5 seconds until you see on the tablet screen the black screen with the writing "POWERED BY android" in white at the bottom. You are now in bootloader mode.
3. Connect the tablet via USB to your PC
4. Download and decompress: SmartTab4G_Recovery_KK_benjaminwan_EN.zip
5. In command line in a terminal window on your PC type:
fastboot -i 0x1bbb oem unlock
fastboot -i 0x1bbb boot cwm.img
wait a little and then you will see the CWM screen and then install the cm-11-20150714-M12-pop8lte.zip or any other ROM file which must be copied on the microSD TF card you inserted in the tablet. The Google APPS (nano and pico) zip files should also be present on the TF MicroSD. After installing the ROM file from zip on the SD card we need install one of the GAPPS files. I personally installed the pico to have more space on the /system partition.[/QUOTE]
I did the whole procedure but has not been successful
this is the detail
c:\vodafone>fastboot -i 0x1bbb oem unlock
...
okay [ 0.004s]
finished. total time: 0.005s
c:\vodafone>fastboot -i 0x1bbb boot cwm.img
downloading 'boot.img'
FAILED (command write failed (unknown error))
finished. total time: 5.005s
Please can you help me?
what is wrong?
Thanks
I did this same procedure that I mentioned with exactly the same files that you downloaded from the mediafire links I gave out and here is the results the tablet returned to the PC terminal. My PC is running Linux by the way but the result should be the same in Windows if the drivers for the tablet are installed correctly:
Latitude-D820# fastboot -i 0x1bbb oem unlock
...
OKAY [ 0.003s]
finished. total time: 0.003s
Latitude-D820# fastboot -i 0x1bbb boot cwm.img
downloading 'boot.img'...
OKAY [ 0.497s]
booting...
OKAY [ 0.090s]
finished. total time: 0.587s
Please make sure you have installed all drivers correctly, that all the files are accessible in their permissions and privileges and that all the files are in the same folder in your PC. What ROM is your smart tab 4 G now running?
cratilo said:
[/COLOR]
I did the whole procedure but has not been successful
this is the detail
c:\vodafone>fastboot -i 0x1bbb oem unlock
...
okay [ 0.004s]
finished. total time: 0.005s
c:\vodafone>fastboot -i 0x1bbb boot cwm.img
downloading 'boot.img'
FAILED (command write failed (unknown error))
finished. total time: 5.005s
Please can you help me?
what is wrong?
Thanks
Click to expand...
Click to collapse
Connect ONLY the Vodafone Smart Tab 4G to your PC and in command line in a terminal window on your PC type:
fastboot oem unlock
fastboot boot cwm.img
all the unzipped files should be in the SAME folder/directory on the PC.
I hope this works for you
---------- Post added at 12:48 PM ---------- Previous post was at 12:38 PM ----------
I also advise you to unplug/remove ALL other USB devices from your PC before booting it up and before trying anything with the tablet.
The only plugged USB device to the PC should be the Vodafone Smart Tab 4G
good luck
solved
I solved with your procedure and the right drivers.
Thanks
cratilo said:
I solved with your procedure and the right drivers.
Thanks
Click to expand...
Click to collapse
good job! I'm glad to have helped you
skaramazoo said:
good job! I'm glad to have helped you
Click to expand...
Click to collapse
cratilo said:
I solved with your procedure and the right drivers.
Thanks
Click to expand...
Click to collapse
And where is the right drivers? My Vodafone Smart Tab 4g P353X is bricked and the only connection that i have is for QDLoader 9008 with QPST. How to establish connection for ADB?
Now in device manager i can get Android Bootloader Interface after installing official POP 8S drivers, but i still can`t get the device to be listed in ADB... and to see the tablet in device manager i have to hold power+vol down. Power+vol up=recovery mode and vol up+vol down= qdloader 9008(download mode for Qualcomm).
m.slavov said:
And where is the right drivers? My Vodafone Smart Tab 4g P353X is bricked and the only connection that i have is for QDLoader 9008 with QPST. How to establish connection for ADB?
Now in device manager i can get Android Bootloader Interface after installing official POP 8S drivers, but i still can`t get the device to be listed in ADB... and to see the tablet in device manager i have to hold power+vol down. Power+vol up=recovery mode and vol up+vol down= qdloader 9008(download mode for Qualcomm).
Click to expand...
Click to collapse
How did your Vodafone Smart Tab 4G get bricked?
I would propose you to consider to connect it to a Linux PC (running Linux Mint for example) and install the latest ADB package on it and then connect your Vodafone Smart Tab 4G.
In Linux you don't need any drivers.
Hi everyone, a little bit off topic but related to this tablet: does this tablet have the vibration and and the brightness sensor?
Thanks
sverza said:
Hi everyone, a little bit off topic but related to this tablet: does this tablet have the vibration and and the brightness sensor?
Thanks
Click to expand...
Click to collapse
This tablet does not support vibration. Automatic brightness, yes.
skaramazoo said:
This tablet does not support vibration. Automatic brightness, yes.
Click to expand...
Click to collapse
Thanks, about display why I can't see any options related to the automatic brightness?
sverza said:
Thanks, about display why I can't see any options related to the automatic brightness?
Click to expand...
Click to collapse
oops no! automatic brightness is not available on this tablet. my mistake. I am using other ROM which has such an option in the picture you sent but it does not work
so, no. auto brightness is not supported here. no such sensor.
skaramazoo said:
oops no! automatic brightness is not available on this tablet. my mistake. I am using other ROM which has such an option in the picture you sent but it does not work
so, no. auto brightness is not supported here. no such sensor.
Click to expand...
Click to collapse
Thanks again.
Are other roms extremely better than the stock Vodafone?
sverza said:
Thanks again.
Are other roms extremely better than the stock Vodafone?
Click to expand...
Click to collapse
you're welcome.
my personal view is that, yes, they are better because they work much faster with less computing overhead for the tablet providing at the same time more features.
one however, need be extra careful when flashing those ROMs to the tablet in order not to cause damage and brick it.
skaramazoo said:
Connect ONLY the Vodafone Smart Tab 4G to your PC and in command line in a terminal window on your PC type:
fastboot oem unlock
fastboot boot cwm.img
all the unzipped files should be in the SAME folder/directory on the PC.
I hope this works for you
---------- Post added at 12:48 PM ---------- Previous post was at 12:38 PM ----------
I also advise you to unplug/remove ALL other USB devices from your PC before booting it up and before trying anything with the tablet.
The only plugged USB device to the PC should be the Vodafone Smart Tab 4G
good luck
Click to expand...
Click to collapse
Hello!
I have an issue with the process.
I have unziped the file SmartTab4G_Recovery_KK_benjaminwan_EN , on my desktop , and then I'm opening the cmd on my pc and then I'm typing the 2 commands :
fastboot oem unlock
fastboot boot cwm.img , but I'm getting a message :
C:\Users\djsbe>fastboot oem unlock
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Can you please help me?
Also , what is the purpose of the SmartTab4G_Recovery_KK_benjaminwan_EN ? Do I have to execute a file in order to proceed?
djbeast said:
Hello!
I have an issue with the process.
I have unziped the file SmartTab4G_Recovery_KK_benjaminwan_EN , on my desktop , and then I'm opening the cmd on my pc and then I'm typing the 2 commands :
fastboot oem unlock
fastboot boot cwm.img , but I'm getting a message :
C:\Users\djsbe>fastboot oem unlock
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Can you please help me?
Also , what is the purpose of the SmartTab4G_Recovery_KK_benjaminwan_EN ? Do I have to execute a file in order to proceed?
Click to expand...
Click to collapse
Inside the folder of the unzipped SmartTab4G_Recovery_KK_benjaminwan_EN file there are all the commands necessary. fastboot, adb... see the attached png file.
Hi
I used my Xiaomi Redmi Note 3, 3GB RAM, 32GB new phone first day yesterday.
When I went to sleep it was 92% charged and when I woke up it was stuck on the Xiaomi loading screen. I let it on that screen for about 3 hours before I restarted it.
It's unable to boot into normal mode, and when I try to get into recovery mode it just shows a screen to connect a cable.
When I connect the cable to the computer it shows that the cable is connected but nothing happens after this.
If I boot the phone in fastboot and use Mi PC Suite to try to flash it, it just tells me to reboot in normal mode and try again.
If I hold all 3 buttons I have managed to get into some test mode, but from there I can't do anything.
How can I reset or get into my phone again? Is this normal behaviour after just one day use?
Johanna12221 said:
Hi
I used my Xiaomi Redmi Note 3, 3GB RAM, 32GB new phone first day yesterday.
When I went to sleep it was 92% charged and when I woke up it was stuck on the Xiaomi loading screen. I let it on that screen for about 3 hours before I restarted it.
It's unable to boot into normal mode, and when I try to get into recovery mode it just shows a screen to connect a cable.
When I connect the cable to the computer it shows that the cable is connected but nothing happens after this.
If I boot the phone in fastboot and use Mi PC Suite to try to flash it, it just tells me to reboot in normal mode and try again.
If I hold all 3 buttons I have managed to get into some test mode, but from there I can't do anything.
How can I reset or get into my phone again? Is this normal behaviour after just one day use?
Click to expand...
Click to collapse
Flash aboot it will ok..
Hi and thanks for your reply!
By running fastboot getvar product I found out that I have the "special edition" model, kate.
I have now downloaded this:
kate_global_images_6.9.8_20160805.0000.29_6.0_global_042c784ac4
After unpacking and trying to flash I get this:
Code:
fastboot flash tz C:\kate\kate\images\tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (637 KB)...
OKAY [ 0.023s]
writing 'tz'...
FAILED [B](remote: Critical partition flashing is not allowed)[/B]
finished. total time: 0.032s
"Flash tz error"
Johanna12221 said:
Hi and thanks for your reply!
By running fastboot getvar product I found out that I have the "special edition" model, kate.
I have now downloaded this:
kate_global_images_6.9.8_20160805.0000.29_6.0_global_042c784ac4
After unpacking and trying to flash I get this:
Code:
fastboot flash tz C:\kate\kate\images\tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (637 KB)...
OKAY [ 0.023s]
writing 'tz'...
FAILED [B](remote: Critical partition flashing is not allowed)[/B]
finished. total time: 0.032s
"Flash tz error"
Click to expand...
Click to collapse
By looks of it, you have a locked bootloader and hence, are unable to flash fastboot files. The only way for you to make your device usable again is to somehow boot into the 'edl' mode and use MiFlash to falsh the fastboot ROM from there.
Hi! Thanks for your reply.
I didn't do anything to the bootloader, so yeah it should be locked.
I will contact the store I bought it from and try to get it returned.
So sad to have made this purchase. I hope I can find another phone, perhaps one that is not as cheap as this.
Hi again!
I have kept trying to solve this issue further. I'm able to get into edl mode using the modified fastboot that I found here on the forums with "fastboot reboot-edl".
I managed to run MiFlash 2016.04.01 (important, newer version didn't work!)
But it still seems to be stuck in just an endless Android loading screen. Anything else I can try?
Johanna12221 said:
Hi again!
I have kept trying to solve this issue further. I'm able to get into edl mode using the modified fastboot that I found here on the forums with "fastboot reboot-edl".
I managed to run MiFlash 2016.04.01 (important, newer version didn't work!)
But it still seems to be stuck in just an endless Android loading screen. Anything else I can try?
Click to expand...
Click to collapse
I can help you. Talk me in PM.
Hi!
Thanks for offering your help, andersonaragao.
I finally got it to work by doing a "Flash all" of the MIUI 8 package.
So the steps so solve was just this easy:
Boot in fastboot (Volume down + power)
Make sure you have kenzo or kate (fastboot getvar product)
Get correct fastboot rom, depending on kenzo/kate: (http://en.miui.com/a-234.html)
Boot in edl (Fastboot_edl-v2: fastboot reboot-edl)
MiFlash 2016.04.01 (Flash all)
Hello there!
Long story short:
I'm was successfully running on twrp-3.0.2-0-onyx-20161020-085152.img and cm-13 on my beloved OPX for serveral months now. Got it running, following this guides:
http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
https://wiki.cyanogenmod.org/w/Install_CM_for_onyx
Also, happily updating the nightly builds since then.
But last update went wrong. I OTA updated my device on the go, not paying to much attention that the update will be cm13->cm14. After TWRP installed the update i got stuck on reboot with the OnePlus logo.
I restarted the phone (Powerbutton off/on), 'cause my guts told me that something went wrong. I hoped to reboot to recovery an rollback the update to previous CM version.
But, it won't boot.
This is what happens:
Powerbutton down (Trun on): -> Vibrates -> flashes OP Logo + powerd by Android -> Vibrates -> flashes OP Logo + powerd by Android ->...
I can reach fastboot mode by VolumeUp (w/o pressing powerbutton) but i cannot reach TWRP recovery.
So normally i could totally live with fastboot, flashing reflashing unlocking etc. BUT here my first WTF experience took place:
I can not
Code:
fastboot oem unlock
because oem unlock is locked! I know how to unlock it via DevMode -> unlock oem unlock yadda yadda (who had this "great" idea anyway?!). But since i cannot boot the OS, i cannot enter devmode....
So before going through all the (Mega)unbrick guides, I'm curious:
Is there some way around this dilemma?
What we've got: No OS, no recovery, only fastboot
Code:
$: fastboot devices
...
25bf1e07 fastboot
$ fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.006s]
finished. total time: 0.006s
$: fastboot oem unlock
...
FAILED (remote: oem unlock is disabled)
finished. total time: 0.003s
$: fastboot format userdata
Creating filesystem with parameters:
Size: 12611891200
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3079075
Block groups: 94
Reserved block group size: 751
Created filesystem with 11/770048 inodes and 88617/3079075 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.000s
Code:
fastboot continue
ends up in same loop.
I cannot adb.
Device is encrypted.
I've no problem to completely wipe or factory reset or stock reset my device, hence i love tinkering with it and have backups of important data.
I sincerely ask for some pointers, links, opinions on how to go on from here? Is there a chance to get my phone back running? Should I stop searching and just follow the unbrick guides?
Are there unbrick guides for Linux users? (Just nice to have! )
Is there some exploit, backdoor, trick, magic to circumvent a disabled 'oem unlock'? (again: who had this 'great' idea anyways? )
Unbrick guide(s):
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
Thank you very much in advance! Have your (virtual) coffee on me!
sem
Hi,
I do have the very same issue.
I can enter fastboot but that's about it. Would be curious to get it running again without the "mega unbrick" stuff...
I found a way to get back.
After i have flashed to CM 14.1 Nightly update it was stuck at the oneplus logo, and i felt the same that something went wrong had no other choice just rebooted the phone and then it started acting wired (Phone vibrates and it shows oneplus logo for every second) and not able to access TWRP. Only i can access is Fast boot but here is the twist the oem was locked and we cannot unlock it any way.
Spent lot of time (2hrs+) searching for the solution and finally found it :angel:
Check this Link
forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
It took me around 4hrs to get back to my Custom Rom
Cheers
i'm suffering the same problem now...today morning tried to update the cm nightly 14 and soft bricked my oneplus X
is the mega unbrick guide really working..? for me device is not recognized when i connect the phone to the pc pressing v up key for 10 secs..
prasannazx said:
i'm suffering the same problem now...today morning tried to update the cm nightly 14 and soft bricked my oneplus X
is the mega unbrick guide really working..? for me device is not recognized when i connect the phone to the pc pressing v up key for 10 secs..
Click to expand...
Click to collapse
Which driver you are using and which windows version 64bit or 32bit?
prasannazx said:
i'm suffering the same problem now...today morning tried to update the cm nightly 14 and soft bricked my oneplus X
is the mega unbrick guide really working..? for me device is not recognized when i connect the phone to the pc pressing v up key for 10 secs..
Click to expand...
Click to collapse
Just flash Arsenic Kernel for Android N. Cyanogen 14 has kernel problem. Flashing custom kernel will fix your bugged boot
Caraparbor said:
Just flash Arsenic Kernel for Android N. Cyanogen 14 has kernel problem. Flashing custom kernel will fix your bugged boot
Click to expand...
Click to collapse
Thnx man!! It helped me not to waste my time doing this mega unbrick process...
Caraparbor said:
Just flash Arsenic Kernel for Android N. Cyanogen 14 has kernel problem. Flashing custom kernel will fix your bugged boot
Click to expand...
Click to collapse
Thank you...? ?
does the clock app and settings for gboard work ????
does the clock app and settings for gboard work ????
Caraparbor said:
Just flash Arsenic Kernel for Android N. Cyanogen 14 has kernel problem. Flashing custom kernel will fix your bugged boot
Click to expand...
Click to collapse
But is flashing a kernel possible w/o oem unlock?
prasannazx said:
i'm suffering the same problem now...today morning tried to update the cm nightly 14 and soft bricked my oneplus X
is the mega unbrick guide really working..? for me device is not recognized when i connect the phone to the pc pressing v up key for 10 secs..
Click to expand...
Click to collapse
Press VolUp until you see something in Devicemanager! It took more than 10s for me too until it showed up in Devicemanager.
Or if you have a Linux at hand, look at dmesg. You should see something like this:
Code:
[ +0,004635] usbcore: registered new interface driver qcserial
[ +0,000049] usbserial: USB Serial support registered for Qualcomm USB modem
[ +0,000103] qcserial 1-4:1.0: Qualcomm USB modem converter detected
[ +0,000325] usb 1-4: Qualcomm USB modem converter now attached to ttyUSB0
[Dec24 02:39] usb 1-4: USB disconnect, device number 6
[ +0,000343] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
Ashok6086 said:
After i have flashed to CM 14.1 Nightly update it was stuck at the oneplus logo, and i felt the same that something went wrong had no other choice just rebooted the phone and then it started acting wired (Phone vibrates and it shows oneplus logo for every second) and not able to access TWRP. Only i can access is Fast boot but here is the twist the oem was locked and we cannot unlock it any way.
Spent lot of time (2hrs+) searching for the solution and finally found it :angel:
Check this Link
forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
It took me around 4hrs to get back to my Custom Rom
Cheers
Click to expand...
Click to collapse
I was stuck on OnePlus logo too, but I solved the situation pushing a different recovery throgh fastboot commands, then I've installed a different ROM. It took me only 5 minutes!
When you restart your bricked device (pressing for 12 seconds the power btn) keep pressed the Volume UP BTn to enter the Fastboot Mode, the follow the procedure to flash a different recovery.
I'm using BlueSpark TWRP Recovery. As ROM, for now, I'm using XperienceRom with Android 7.1 and no bug found.
I tried that too, but no use. it says OEM Locked and we cannot unlock the phone that means we cannot load anything.
Ashok6086 said:
I tried that too, but no use. it says OEM Locked and we cannot unlock the phone that means we cannot load anything.
Click to expand...
Click to collapse
Use megha unbrick guide
http://forum.xda-developers.com/one...ga-unbrick-guide-hard-bricked-t3272108/page20
I had the same problem. Solved it by first flashing latest cm and right after that I flash arsenic kernel and then reboot. I had to do that every time I flash a new nightly build but it works. Hope it helps
Hello.
I've had the exact same problem as semph0re.
Did the Mega Unbrick Guide thing, somehow I got a "Sahara communication failed" during the process, but it still managed to flash the stock recovery (and the old bootloader i guess).
From there I'm able to install and successfully boot OOS 2.3 (or older), old versions of CM13.0 (those based on the old bootloader), and TWRP-3.0.2-0 recovery and therefore unlock the bootloader.
So basically anything compatible with the old bootloader.
And trying to install anything based on the new bootloader, either a stock rom, the OPX_MM_recovery from Oneplus, any custom rom, with or without custom kernel or a custom recovery leave me with a fixed Oneplus logo (and the powered by android disappearing almost immediately)
But I can't manage to update the bootloader.
Either by trying to install OOS3.1.x from OOS 2.x
Nor by following matwaking guidehttps://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Does anyone have face the same issue ? Any idea what could the cause of the problem ?
The only thing I could think of but didn't try is to go through the Mega Unbrick guide again. But I'm on Ubuntu and do not have a Windows machine anywhere near me at the moment.
@GARGZUL you have to use stock recovery from 2.X.X not mm stock.
Exodusche said:
@GARGZUL you have to use stock recovery from 2.X.X not mm stock.
Click to expand...
Click to collapse
@Exodusche
That's what I tried many times.
Trying to install OOS3.x from OOS2.x with either (old)stock recovery or TWRP-3.0.2-0 leave me with a beautiful stuck Oneplus logo when booting system.
And those are the only recovery I can boot on. Any more recent recovery won't boot (fixed Oneplus logo again or 'dtb not found' error when boot from fastboot command) since they require the new BL.
It's like when trying to install OOS3.x or flashing matwaking's BLUpdater.zip the old bootloader is not deleted, effectively preventing any new BL based rom or recovery to boot.
@GARGZUL Use latest twrp and you want to use 2.2.3 before flashing 3.X.X .
Exodusche said:
@GARGZUL your using the wrong twrp use 3.0.3
Click to expand...
Click to collapse
@Exodusche
I would if I could. But when flashing TWRP 3.0.3-0 (either with flashboot or via TWRP 3.0.2-0) my phone won't boot to recovery (Vol down+poweer gives me a stuck oneplus logo, and 'fastboot boot twrp-3.0.3-0-onyx.img' gives me a "dtb not found" error).
Any other idea ?