I've been trying to push the bootloader and radio from the 4.2.2 factory image using fastboot using the commands below
fastboot flash radio "filename.img"
fastboot flash hboot "filename.img"
The radio works just fine, but while flashing the bootloader it gives me an error saying "partition table doesn't exist".
Any idea what this means and how it can be fixed?
AW: Fastboot - Partition table doesn't exist
Hboot is HTC. On Nexus 4 it is
Code:
fastboot flash bootloader bootloader.img
Sent from my Nexus 4 using xda premium
hboot is HTC. for N4 you use
fastboot flash boot boot.img
boot.img is whatever your bootloader image is. Please note:flashing wrong/corrupted boot.img is difficult to recover.
siddjazz said:
fastboot flash hboot "filename.img"
The radio works just fine, but while flashing the bootloader it gives me an error saying "partition table doesn't exist".
Any idea what this means and how it can be fixed?
Click to expand...
Click to collapse
Sent from my Nexus 4 in a Faraday cage
KyraOfFire said:
hboot is HTC. for N4 you use
fastboot flash boot boot.img
boot.img is whatever your bootloader image is. Please note:flashing wrong/corrupted boot.img is difficult to recover.
Sent from my Nexus 4 in a Faraday cage
Click to expand...
Click to collapse
No
boot is the kernel.
bootloader is the bootloader.
There is no "bootloader" partition. Good luck flashing on that. Nexus 4 mount point thread:
http://forum.xda-developers.com/showpost.php?p=34141701&postcount=1
Nuu~ said:
No
boot is the kernel.
bootloader is the bootloader.
Click to expand...
Click to collapse
Sent from my Nexus 4 in a Faraday cage
Nuu~ said:
No
boot is the kernel.
bootloader is the bootloader.
Click to expand...
Click to collapse
So the command would be fastboot flash bootloader "boot.img" ?
This is a bit confusing
siddjazz said:
So the command would be fastboot flash bootloader "boot.img" ?
This is a bit confusing
Click to expand...
Click to collapse
fastboot flash bootloader bootloader-mako-makoz10o.img
and for the radio:
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
KyraOfFire said:
There is no "bootloader" partition. Good luck flashing on that. Nexus 4 mount point thread:
http://forum.xda-developers.com/showpost.php?p=34141701&postcount=1
Click to expand...
Click to collapse
is that so? =)
even if there is no "bootloader" partition, fastboot still flashes the right partition when used with "flash bootloader".
KyraOfFire said:
hboot is HTC. for N4 you use
fastboot flash boot boot.img
boot.img is whatever your bootloader image is. Please note:flashing wrong/corrupted boot.img is difficult to recover.
Sent from my Nexus 4 in a Faraday cage
Click to expand...
Click to collapse
You're gonna make someone brick their device. Do us all a favor and stick to toolkits. Please.
It's definitely most ****ing definitely:
Code:
fastboot flash bootloader bootloader.img
KyraOfFire said:
hboot is HTC. for N4 you use
fastboot flash boot boot.img
boot.img is whatever your bootloader image is. Please note:flashing wrong/corrupted boot.img is difficult to recover.
Click to expand...
Click to collapse
NO!
Your advice above is totally wrong, and will brick a phone if it is followed. Boot is the kernel, NOT the bootloader.
Sent from my Nexus 4
starscream92 said:
You're gonna make someone brick their device. Do us all a favor and stick to toolkits. Please.
It's definitely most ****ing definitely:
Code:
fastboot flash bootloader bootloader.img
[/QUOTe
Lmfao
I guess toolkits do have a purpose
i gave you a thanks for the laugh
Click to expand...
Click to collapse
I followed his instructions
I followed his instructions and used fastboot flash boot boot.img
Is it hopeless and I need to buy a new phone or is their still hope?
Oddly, it seemed to allow me to use the correct method fastboot flash bootloader boot.img, bu I get stuck in a bootloop.
If anyone could help me that would be greatly appreciated.
qsylalyn said:
I followed his instructions and used fastboot flash boot boot.img
Is it hopeless and I need to buy a new phone or is their still hope?
Oddly, it seemed to allow me to use the correct method fastboot flash bootloader boot.img, bu I get stuck in a bootloop.
If anyone could help me that would be greatly appreciated.
Click to expand...
Click to collapse
boot = kernel
bootloader = bootloader
radio = modem
userdata = nand´s user data storage(/data)
system = system
cid = not used on n4
so for god sake
just install stock images
its pretty straitgh forward, just double click on .bat
qsylalyn said:
I followed his instructions and used fastboot flash boot boot.img
Is it hopeless and I need to buy a new phone or is their still hope?
Oddly, it seemed to allow me to use the correct method fastboot flash bootloader boot.img, bu I get stuck in a bootloop.
If anyone could help me that would be greatly appreciated.
Click to expand...
Click to collapse
Of course you're in a boot loop. You still have the bootloader image in your kernel because that's where you flashed it to!
Wouldn't the solution be to get a KERNEL image and flash that to the BOOT partition before you flash your bootloader image to its correct partition (bootloader) which is what you now doing?
You never posted back on where you ended up with your phone.
Related
So I used the Nexus Root Toolkit to flash stock and unroot it, but after using it, I got stuck at the bootloader screen. So I pushed the start button to reboot, and my nexus 7 is still rooted. Help plz?
Give it a try again? I have use this 5 times, work great for me, u have adb fastboot mode on ur desktop?
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Download the stock image and flash in fastboot .
Sent from my Nexus 7 using xda premium
So when i try to fastboot the bootloader .img manually, it says:
sending bootloader ... okay
'writing bootlader'.... failed (remote: (invalid state))
so what do i need to do to fix that?
zeiloz said:
So when i try to fastboot the bootloader .img manually, it says:
sending bootloader ... okay
'writing bootlader'.... failed (remote: (invalid state))
so what do i need to do to fix that?
Click to expand...
Click to collapse
Is your bootloader locked?
Sent from my Nexus 7 using xda premium
it said lock status: unlock
So i would presume its unlocked...
zeiloz said:
it said lock status: unlock
So i would presume its unlocked...
Click to expand...
Click to collapse
OK. I've never seen that error before. And a quick google search doesn't come up with anything either.
You could try restarting the bootloader with
Code:
fastboot reboot-bootloader
and trying again.
The only thing I can think of is you could be trying to flash the wrong bootloader (which i doubt) Just to confirm you are trying to flash bootloader-grouper-3.34.img
Also, to just unroot you don't need to reflash the bootloader. Just boot.img and system.img
El Daddy said:
OK. I've never seen that error before. And a quick google search doesn't come up with anything either.
You could try restarting the bootloader with
Code:
fastboot reboot-bootloader
and trying again.
The only thing I can think of is you could be trying to flash the wrong bootloader (which i doubt) Just to confirm you are trying to flash bootloader-grouper-3.34.img
Also, to just unroot you don't need to reflash the bootloader. Just boot.img and system.img
Click to expand...
Click to collapse
Yes, I am trying to flash bootloader.grouper-3.34.img
And Im flashing bootloader because its I'm told to do in this thread? http://forum.xda-developers.com/showthread.php?t=1781250
I will try what you told me and see if it will work
So i rebooted the bootloader, and it still gives me the same thing. Whats the command to boot.img and system .img?
zeiloz said:
So i rebooted the bootloader, and it still gives me the same thing. Whats the command to boot.img and system .img?
Click to expand...
Click to collapse
Both the boot.img and the system.img are in the image-nakasi-jro03d.zip you must extract them first.
Then run: fastboot devices (to make sure you're connected) if it returns the serial number then proceed.
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot erase cache
fastboot reboot
This should maintain your data and unroot your nexus.
However, I am a bit concerned about the invalid state error. I can't find anything about it at all. I'm worried your nand might be corrupted and proceeding with this might lead to an unrecoverable state. Maybe someone else can weigh in on this... I don't want to scare you but I don't want to be responsible if something goes wrong.
hmm... I hope more people would weigh in on this? Cuz im exchanging the nexus 7 due to flickering screens, and im new to the rooting/unrooting stuff so i dont want to brick this device cuz im a n00b.
hmm... I hope someone else weigh in on this to help, cuz I'm going to exchange this nexus 7 for another 1 because of flickering issues...
Restart, carefully check
My nexus had the ghosting issue and I had to unroot my device to ship back today. Heres how I did it.
1. Download stock ROM from Google.
2. Unzip stock ROM from Google. The unzipped file will have 4 files in it. (Boot loader grouper image, flash all.sh, flash base.sh and the image.zip)
3. Unlock your device by clicking the unlock button on nexus root toolkit
4. When your device wakes turns on set it back up. No need to log into Google.
5. turn a dB back on in development
6. Click flash stock + unroot
7. click other/browse
8. For choice click I did this already.
9. Click OK
10. browse to your unzipped file location with the 4 files in it.
11. click OK
12. Done
Sent from my Desire HD using xda premium
I'm facing a similar problem.
http://forum.xda-developers.com/showthread.php?p=31128926
Did you find a way to flash the Bootloader?
I'm thinking about a hardware issue as well. Are there any Devices, with corrupted NAND's known?
Marcus
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
Hi all,
on my Nexus 9, update to LRX21Q failed: After reboot, the android icon was shown with "error" below.
I suppose, update failed as my system is rooted with the method Chainfire posted in the development forum.
After an additional reboot, the previous firmware is still shown. The system does not offer the update anymore but claims to be up-to-date.
Any hints? Thanks in advance.
Maybe it's the modified kernel from Chainfire. Try to get back to the stock kernel and try again.
Download the factory image, flash recovery, boot, system & vendor.
Your software will be updated and you won't lose any data. You will lose root however.
I got the same error from OTA with no root. Only had 9 for 2 days, got OTA rite out of box no issue.
Yesterday for new build i get little error android icon upon reboot/install.
Obviously, something that is being changed by the "root" process is being checked DURING the update process. Probably a checksum on the boot partition. If it doesn't match, it bails on the update.
The likely reason for this is they acknowledge that you don't want to lose your root.
All it means is that you need to do the update manually.
It may be possible for a modified recovery to bypass this check, or possibly even be made to auto-root new boot images.
Thanks, guys. Will try as suggest above and post results.
Update: worked perfectly, needed to root again though.
StuMcBill said:
Download the factory image, flash recovery, boot, system & vendor.
Your software will be updated and you won't lose any data. You will lose root however.
Click to expand...
Click to collapse
has anyone tried this? i would like to update without losing data...
Flash through fastboot and you will be fine. Thats what I did then rerooted with CF autoroot
mk92595 said:
Flash through fastboot and you will be fine. Thats what I did then rerooted with CF autoroot
Click to expand...
Click to collapse
What's the fastboot command for the img? Do you flash as boot, system, etc?
zeebone said:
What's the fastboot command for the img? Do you flash as boot, system, etc?
Click to expand...
Click to collapse
Fastboot flash bootloader bootloader.img
Fastboot reboot-bootloader
Fastboot flash system system.img
Fastboot reboot-bootloader
Fastboot flash boot boot.img
Fastboot reboot-bootloader
Fastboot flash vender vendor.img
Fastboot reboot-bootloader
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot reboot
Not sure if I forgot one but I think thats all of them
mk92595 said:
Fastboot flash bootloader bootloader.img
Fastboot reboot-bootloader
Fastboot flash system system.img
Fastboot reboot-bootloader
Fastboot flash boot boot.img
Fastboot reboot-bootloader
Fastboot flash vender vendor.img
Fastboot reboot-bootloader
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot reboot
Not sure if I forgot one but I think thats all of them
Click to expand...
Click to collapse
Should there be a - sign between reboot and bootloader .. And is fastboot flash vender or vendor... Just making sure .
pantmunu said:
Should there be a - sign between reboot and bootloader .. And is fastboot flash vender or vendor... Just making sure .
Click to expand...
Click to collapse
Yes there should be a - sign and vendor. Sorry i'm not home so I don't have the files near me.
mk92595 said:
Yes there should be a - sign and vendor. Sorry i'm not home so I don't have the files near me.
Click to expand...
Click to collapse
Thank you sir .
Where can i find the images for download. Thx
Google for nexus factory image.
Sent from my Nexus 9 using XDA Premium HD app
Update failed on me too. Completely stock
UPDATE:
Apparently *some* devices didn't get the recovery updated with the last update (LRX21L).
The new update (LRX21Q) requires the newer version of the recovery to install.
Google really messed up the launch of the Nexus 9 with all the HW/SW quality control issues
Serious f#ck-up from Google really
Interesting thing I noticed: I restored factory images manually in order to unroot and the OTA was no longer available. I verified I was still running on L. I manually installed the update and it went in just fine.
Now waiting on the root package to be updated for the Q kernel. You can re-root but you will be running on the L kernel, not the Q kernel.
maarten08 said:
Update failed on me too. Completely stock
Click to expand...
Click to collapse
My too fck Google
Mine failed and Im not even rooted
And im not sure if it did the update as its not showing a new one. Im on L
So i was recording a video, when it entered a state where I had to reboot the phone. I did so, and it got stuck. I did a hard reset. The phone then gets stuck at bootloader unlocked. I entered fastboot, selected recovery, and it gets stuck at the twrp logo. Any ideas? I also re-flashed twrp and it still get stuck.
Can you boot TWRP with 'fastboot boot twrp.img' and do anything? (Replace 'twrp.img' with your TWRP image filename)
If not, try fastboot flashing back to stock, but it kind of sounds like your emmc (internal storage chip) might have take a dump. Very unusual, but not unheard of.
acejavelin said:
Can you boot TWRP with 'fastboot boot twrp.img' and do anything? (Replace 'twrp.img' with your TWRP image filename)
If not, try fastboot flashing back to stock, but it kind of sounds like your emmc (internal storage chip) might have take a dump. Very unusual, but not unheard of.
Click to expand...
Click to collapse
I used a restore-to-stock tool. It didn't actually restore me to stock. I have NO CLUE what it did, but suddenly i saw my custom boot animation again, and was able to boot into twrp, altough my nandroids are gone. I flashed a rom, and it didn't recognize the sim card. I flashed a new rom, and it recognizes the card, but i get no service (in my house where i always get service). Any ideas?
thebaconbox said:
I used a restore-to-stock tool. It didn't actually restore me to stock. I have NO CLUE what it did, but suddenly i saw my custom boot animation again, and was able to boot into twrp, altough my nandroids are gone. I flashed a rom, and it didn't recognize the sim card. I flashed a new rom, and it recognizes the card, but i get no service (in my house where i always get service). Any ideas?
Click to expand...
Click to collapse
This is why one-click tools are bad... You need to flash the full stock image manually, and not downgrade, you must use the same or newer version of stock firmware than you device last had installed.
acejavelin said:
This is why one-click tools are bad... You need to flash the full stock image manually, and not downgrade, you must use the same or newer version of stock firmware than you device last had installed.
Click to expand...
Click to collapse
How do I do that?
thebaconbox said:
How do I do that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/mot...de-return-to-stock-relock-bootloader-t3489110
acejavelin said:
http://forum.xda-developers.com/mot...de-return-to-stock-relock-bootloader-t3489110
Click to expand...
Click to collapse
Could I just flash the NON-HLOS.bin modem in fastboot and nothing else?
thebaconbox said:
Could I just flash the NON-HLOS.bin modem in fastboot and nothing else?
Click to expand...
Click to collapse
No, I don't think so, but you could do it like this:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin (optional)
acejavelin said:
No, I don't think so, but you could do it like this:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin (optional)
Click to expand...
Click to collapse
And i can do this with twrp installed and the pure nexus custom rom installed and it should work just fine?
thebaconbox said:
And i can do this with twrp installed and the pure nexus custom rom installed and it should work just fine?
Click to expand...
Click to collapse
Yes
acejavelin said:
Yes
Click to expand...
Click to collapse
Alright, I flashed everything and my cell service now works flawlessly.
thebaconbox said:
Alright, I flashed everything and my cell service now works flawlessly.
Click to expand...
Click to collapse
Awesome!
hy,
my purenexus rom was running perfectly but today i was installing spotify and it hanged and then i had to retsart but now it stucks on bootloader warning screen .recvory also stucks on twrp logo . now what should i do .i googled and found this thread.please guide me which thread do i need to follow ..will my bootloader get locked again ? where do i have to start it from? i also have nandroid backup of previous custom rom which is truepure rom. please guide me.
Flash(with fastboot) again twrp(wipe system, cache, data, dalvik) and restore your backup. @azzammalik
dzidexx said:
Flash(with fastboot) again twrp(wipe system, cache, data, dalvik) and restore your backup. @azzammalik
Click to expand...
Click to collapse
if i flash twrp again then it would stuck again on twrp logo as this op suggested . by flashing through fastboot you meant stock firmware then can you please guide me which file i have to download so i can just flash it using fastboot. and is there any way so i dont loose my data thanks
azzammalik said:
if i flash twrp again then it would stuck again on twrp logo as this op suggested . by flashing through fastboot you meant stock firmware then can you please guide me which file i have to download so i can just flash it using fastboot. and is there any way so i dont loose my data thanks
Click to expand...
Click to collapse
Only with twrp you can save your data.
What version did you used? Try with another, maybe don't flash - only boot.
"fastboot boot NameOfTwrp.img"
If it boot copy your data to pc.
Stock you can flash with fastboot, here is "how to", download and flash the highest version for you model:
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
Read carefully, don't lock bootloader.
Hello, I am in dire need of assistance. I'm not sure what I did, but I think i soft bricked my Le Pro 3 LEX727. I was attempting to install a custom rom, I wiped Delvik,system,cache,data then proceeded to flash lineage. When I rebooted it quickled flashed Le Eco bootup then crashed or went to a black screen. Same thing with recovery, quickly flashes "Le Eco Recovery" then goes black. I can boot into Fastboot and the device shows up there, but when I attempt to do "fastboot oem unlock-go" I get "FAILED (remote: oem unlock is not allowed)". Please help me, I really need to fix my phone.
Sincerely,
A grateful person who messed up their phone.
It goes into recovery mode? power button + volume up button. redo the procedure and leaves everything in the options selected .. or I hope you made a backup beforehand, there are various discussions on how to recover
If you can access fastboot, youre golden. Just flash a stock rom
trizex said:
If you can access fastboot, youre golden. Just flash a stock rom
Click to expand...
Click to collapse
Can you help me out with where to go from there, or direct me to a thread? When I attempt to unlock oem so i can flash twrp it says "oem unlock is not allowed"
thank you very much.
Gynlemon said:
It goes into recovery mode? power button + volume up button. redo the procedure and leaves everything in the options selected .. or I hope you made a backup beforehand, there are various discussions on how to recover
Click to expand...
Click to collapse
No, it can only boot into fastboot.
Yewsif said:
No, it can only boot into fastboot.
Click to expand...
Click to collapse
https://forum.xda-developers.com/le-pro3/how-to/guide-to-install-stock-rom-custom-t3486600
Gynlemon said:
https://forum.xda-developers.com/le-pro3/how-to/guide-to-install-stock-rom-custom-t3486600
Click to expand...
Click to collapse
Thank you, but as I cant get into the devices OS, I cannot enable usb debugging and oem unlock. Only thing I can access is the fastboot menu.
Have you tried flashing the aboot file? from this thread
fastboot flash aboot emmc_appsboot.mbn
then
reboot
then
Fastboot mode using power-off + volume down.
then
fastboot oem unlock-go
then you can boot or flash into TWRP or whatever recovery
Joms_US said:
Have you tried flashing the aboot file? from this thread
fastboot flash aboot emmc_appsboot.mbn
then
reboot
then
Fastboot mode using power-off + volume down.
then
fastboot oem unlock-go
then you can boot or flash into TWRP or whatever recovery
Click to expand...
Click to collapse
No, I have not. What do you mean the aboot file.
Yewsif said:
No, I have not. What do you mean the aboot file.
Click to expand...
Click to collapse
http://newandroidbook.com/Articles/aboot.html
Joms_US said:
http://newandroidbook.com/Articles/aboot.html
Click to expand...
Click to collapse
Thank you for your time and help, but I have no idea what to do with that link, I understand the adb commands I need to put in. Is there anyway you can sort of walk me through it with steps?
Thank you.
You prolly have more experience than me so I am just pointing to you what I did to unlock the bootloader which seems to be the problem? ^_^
https://forum.xda-developers.com/showpost.php?p=71116203&postcount=8
I gave the instructions and link there already but here is the direct link that contains the aboot file.
https://www.androidfilehost.com/?fid=313042859668275431
joms_us said:
you prolly have more experience than me so i am just pointing to you what i did to unlock the bootloader which seems to be the problem? ^_^
https://forum.xda-developers.com/showpost.php?p=71116203&postcount=8
i gave the instructions and link there already but here is the direct link that contains the aboot file.
https://www.androidfilehost.com/?fid=313042859668275431
Click to expand...
Click to collapse
thank you so much, flashing the aboot file worked and made my custom rom run perfectly! I love you.
Yewsif said:
thank you so much, flashing the aboot file worked and made my custom rom run perfectly! I love you.
Click to expand...
Click to collapse
Thanks would be enough.
Joms_US said:
Have you tried flashing the aboot file? from this thread
fastboot flash aboot emmc_appsboot.mbn
then
reboot
then
Fastboot mode using power-off + volume down.
then
fastboot oem unlock-go
then you can boot or flash into TWRP or whatever recovery
Click to expand...
Click to collapse
I royally messed up my custom ROM install, this got me to boot again. Thank you.
This should be a sticky, or a part of any installation method. Why? If you upgrade to the latest official firmware (e.g. 21s+), your bootloader will no longer be unlocked with the oem unlock-go method. You *have* to flash this bootloader first so you can then unlock it and do all the other steps.
kaivorth said:
I royally messed up my custom ROM install, this got me to boot again. Thank you.
Click to expand...
Click to collapse
Glad this thread helped you.
Joms_US said:
Have you tried flashing the aboot file? from this thread
fastboot flash aboot emmc_appsboot.mbn
then
reboot
then
Fastboot mode using power-off + volume down.
then
fastboot oem unlock-go
then you can boot or flash into TWRP or whatever recovery
Click to expand...
Click to collapse
This works ! Thank you
Joms_US said:
Have you tried flashing the aboot file? from this thread
fastboot flash aboot emmc_appsboot.mbn
then
reboot
then
Fastboot mode using power-off + volume down.
then
fastboot oem unlock-go
then you can boot or flash into TWRP or whatever recovery
Click to expand...
Click to collapse
great thanks for you. I finally unbrick X727 with same way.
Hi guys. Sorry for being noob.
Wanna asking (confused).
My Nexus 7 (2012 Wifi) used Omni Rom 4.4.4
I wanna restore back to Stock Rom.
Do i need to Unroot & Unlock my nexus first before click " flash-all.bat " ??.
I worry might be soft brick if wrong step.
Many many thanks ^_^v
suaji said:
Hi guys. Sorry for being noob.
Wanna asking (confused).
My Nexus 7 (2012 Wifi) used Omni Rom 4.4.4
I wanna restore back to Stock Rom.
Do i need to Unroot & Unlock my nexus first before click " flash-all.bat " ??.
I worry might be soft brick if wrong step.
Many many thanks ^_^v
Click to expand...
Click to collapse
No, you were previously on OmniROM means your bootloader is already unlocked. You just need to boot into bootloader/fastboot mode and flash stock image. Do make sure you have the correct drivers installed. You could use the Universal Naked Drivers if you don't have the correct drivers installed.
rahimali said:
No, you were previously on OmniROM means your bootloader is already unlocked. You just need to boot into bootloader/fastboot mode and flash stock image. Do make sure you have the correct drivers installed. You could use the Universal Naked Drivers if you don't have the correct drivers installed.
Click to expand...
Click to collapse
Noted!.
TQ Sir for replying me ^_^v
i saw inside flash.bat got code :
so that mean i need to do manual oem lock right?.
Code:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasi-lmy47v.zip
suaji said:
Noted!.
TQ Sir for replying me ^_^v
i saw inside flash.bat got code :
so that mean i need to do manual oem lock right?.
Code:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasi-lmy47v.zip
Click to expand...
Click to collapse
If you mean re-lock the bootloader, yes, you will have to do that manually. It's supposed to be a risky procedure so do so at your own risk.
By the way, your signature shows Next 7 3G, that would be the Tilapia rather than Grouper. Make sure before you flash please.
rahimali said:
If you mean re-lock the bootloader, yes, you will have to do that manually. It's supposed to be a risky procedure so do so at your own risk.
By the way, your signature shows Next 7 3G, that would be the Tilapia rather than Grouper. Make sure before you flash please.
Click to expand...
Click to collapse
thanks for helping sir.
now I can use stock rom back..