Wiped ROM with no ROM on internal SD. - Asus Eee Pad Transformer Prime

I did a System wipe instead of a Factory Reset, and I had no ROM on the internal SD card. Is there anything I can do to get this running again? I can get into twrp v2.1.3.

shadow3352 said:
I did a System wipe instead of a Factory Reset, and I had no ROM on the internal SD card. Is there anything I can do to get this running again? I can get into twrp v2.1.3.
Click to expand...
Click to collapse
The easiest route to go may be to ADB push a ROM to internal then flash it from TWRP. There's plenty of guides on how to ADB push files to the internal memory, so do a search around. Another option is to flash TWRP 2.2.1.4 via fastboot (you'll need to install the AndroidRoot.mobi custom bootloader first) and install a ROM from the external memory. Instructions to install TWRP 2.2.1.4, with a link to the custom bootloader can be found at the following link:
http://www.teamw.in/project/twrp2/93
Good luck!
~Azrael's Kiss~

AzraelsKiss said:
The easiest route to go may be to ADB push a ROM to internal then flash it from TWRP. There's plenty of guides on how to ADB push files to the internal memory, so do a search around. Another option is to flash TWRP 2.2.1.4 via fastboot (you'll need to install the AndroidRoot.mobi customer bootloader first) and install a ROM from the external memory. Instructions to install 2.2.1.4, with a link to the custom bootloader can be found at the following link:
http://www.teamw.in/project/twrp2/93
Good luck!
~Azrael's Kiss~
Click to expand...
Click to collapse
I couldn't find a way to install 2.2.1.4 via fastboot. And as far as ADB goes, I have no idea how to use it. I installed the drivers and everything, but when I do adb devices, nothing shows up under devices attached, but I do see it under device manager.

shadow3352 said:
I couldn't find a way to install 2.2.1.4 via fastboot. And as far as ADB goes, I have no idea how to use it. I installed the drivers and everything, but when I do adb devices, nothing shows up under devices attached, but I do see it under device manager.
Click to expand...
Click to collapse
The link I provided has the instructions for installing TWRP 2.2.1.4. Look again. The GooManager option is out because you don't have an OS, but if you have the custom bootloader (which is recommended) you can flash the img file in the second set of instructions, or it also provides a blob file to flash in the third set of instructions, and finally, if you could get ADB to work, the fourth set of instructions are for ADB installation.
~Azrael's Kiss~

AzraelsKiss said:
The link I provided has the instructions for installing TWRP 2.2.1.4. Look again. The GooManager option is out because you don't have an OS, but if you have the custom bootloader (which is recommended) you can flash the img file in the second set of instructions, or it also provides a blob file to flash in the third set of instructions, and finally, if you could get ADB to work, the fourth set of instructions are for ADB installation.
~Azrael's Kiss~
Click to expand...
Click to collapse
I really appreciate your help. Do you know where I would but the twrp file I would flash? When I do "fastboot -i 0x0b05 flash recovery twrp.blob" or "fastboot -i 0x0b05 flash recovery twrp.img" it just says error: cannot load

shadow3352 said:
I really appreciate your help. Do you know where I would but the twrp file I would flash? When I do "fastboot -i 0x0b05 flash recovery twrp.blob" or "fastboot -i 0x0b05 flash recovery twrp.img" it just says error: cannot load
Click to expand...
Click to collapse
The img or blob file has to be in the same directory as your fastboot binary on your PC.
~Azrael's Kiss~

AzraelsKiss said:
The img or blob file has to be in the same directory as your fastboot binary on your PC.
~Azrael's Kiss~
Click to expand...
Click to collapse
Okay, I got that. It said finished in cmd prompt and now there's a full loading bar on the screen. Should I wait or restart?

AzraelsKiss said:
The img or blob file has to be in the same directory as your fastboot binary on your PC.
~Azrael's Kiss~
Click to expand...
Click to collapse
I got it to work through ADB pushing CM10 on to the internal SD. I really want to thank you for your help.

Related

How to solve Magic Value Mismatch. Solution Here!

Did you get the message: Magic Value Mismatch:-.-.-.-.-.-?!
After flashing a new recovery it happens sometimes.
GREEN ZONE
Are you able to go to the recocery menu(power + vol up)? If not, go to BLUE ZONE. If yes, follow these steps
1. check whether you have copied your rom as "update.zip" to your SD card's root directory
2. Go to recovery menu and install update.zip
BLUE ZONE
You may did something wrong while flashing a new recovery. Here is the right method:
1. go back to fastboot mode(power+power+power+vol up) and type these commands on your PC
2. fastboot erase userdata
3. fastboot erase system
4. fastboot erase cache
5. fastboot erase linux
6. fastboot erase recovery
7. fastboot flash recovery recovery.img (change path, if recovery.img is not in the same directory as fastboot.exe)
8. fastboot reboot
Are you able now to go to the recovery menu? If yes, go to GREEN ZONE and follow steps. If not, go to ORANGE ZONE.
ORANGE ZONE
Are able to unpack the update.zip and find the system.img and boot.img files? If not, then go to RED ZONE. If yes, copy these 2 files to the directory where the fastboot.exe is, run these commands:
1. fastboot erase recovery
2. fastboot flash recovery recovery.img
3. fastboot -w
4. fastboot erase linux
5. fastboot erase system
6. fastboot flash system system.img
7. fastboot flash linux boot.img
8. fastboot reboot
ROM is installed. Enjoy it!
RED ZONE
Make sure, that you copied the same recovery.img to fastboot folder, that you had flashed before to your tablet.
Type this command in recovery mode:
1. fastboot boot recovery.img
This command will run the recovery from your PC. After the recovery menu is booted, go to GREEN ZONE and enjoy your ROM!
If this was helpful to you, please do not hesitate to click on Thanks!
Lol, nice to see my post copy/pasted without any links indicated. Anyway, I hope It's helpful for ppl.
Tried following these steps, however, I'm still getting this error... followed this thread
http://forum.xda-developers.com/showthread.php?t=1470823
installed recovery successfully (via fastboot), and update seems to install fine, until I reboot and get the "Magic Value Mismatch" again..
Any ideas?
yellowumbrella said:
Tried following these steps, however, I'm still getting this error... followed this thread
http://forum.xda-developers.com/showthread.php?t=1470823
installed recovery successfully (via fastboot), and update seems to install fine, until I reboot and get the "Magic Value Mismatch" again..
Any ideas?
Click to expand...
Click to collapse
So you installed the recovery via fastboot. Did you manage to boot into recovery mode?
I had that issue, that I couldn't boot into recovery mod from my Folio, by pressing power+Up button. Thats why I added the RED ZONE method. Its like booting recovery from your PC. (fastboot boot recovery.img). All the times I wanna upgrade my current ROM, I have to do this step, because the power+up does not work, and the Folio skips booting in recovery and wanna do normal booting. However there is no Rom installed on machine, so I get the magic value mismatch message.
So try to boot recovery from your PC, but be sure you have copied to your fastboot folder the same recovery, that you flashed onto the tablet.
I hope it was helpful. If something is not clear, feel free to ask.
Hi there, thanks for the answer.
I am able to install recovery images via fastboot.
Device is showing up as a question mark with >fastboot devices
but recovery installs fine. CWM gives a series of e: can't opne/mount /cache errors.
Foliomod 1.4 installs no problem, thanks to the method here
http://forum.xda-developers.com/showthread.php?t=1458876
yellowumbrella said:
Hi there, thanks for the answer.
I am able to install recovery images via fastboot.
Device is showing up as a question mark with >fastboot devices
but recovery installs fine. CWM gives a series of e: can't opne/mount /cache errors.
Foliomod 1.4 installs no problem, thanks to the method here
http://forum.xda-developers.com/showthread.php?t=1458876
Click to expand...
Click to collapse
Are you able to wipe cache from recovery? And what else errors are listed?
One more thing, try to flash your boot.img and system.img via fastboot as written above.
If I follow this
http://forum.xda-developers.com/showthread.php?t=1458876
and let it install cwm v 3, I get the cache error and cannot wipe or mount via recovery.
If I follow the ICS thread, and flash the new cwm v5 via fastboot, I don't get the cache error, but the rom simply won't start. If I open the package, there is a boot.img, but not a system.img, just a system folder...
I could try flashing boot.img, but I don't see how that could help
yellowumbrella said:
If I follow this
http://forum.xda-developers.com/showthread.php?t=1458876
and let it install cwm v 3, I get the cache error and cannot wipe or mount via recovery.
If I follow the ICS thread, and flash the new cwm v5 via fastboot, I don't get the cache error, but the rom simply won't start. If I open the package, there is a boot.img, but not a system.img, just a system folder...
I could try flashing boot.img, but I don't see how that could help
Click to expand...
Click to collapse
Well just to see it clear. So you are able to install Foliomod 1.4, so your Internal storage is not broken.
When I get home, I will check the system folder of ICS rom. There are some method to create system.img from an unpacked folder...
So, in CWM 5.5.0.4 you manage to install Zip from SD card, ROM and GAPPS as well, but the Rom does not boot?!
yup, that's exactly it.
Haven't tried installing Gapps since I can't even get the rom to boot.
I have a perfectly working tablet with foliomod 1.4, and I did get honeycomb to run but some apps crashed so I reverted back to foliomod.
with CWM CWM 5.5.0.4 everything seems to work great, except at reboot, nothing happens (somehow, I no longer even get the magic value mismatch)
------------------
PS. not sure if this is at all relevant, but I cannot fastboot from win7, I'm fastbooting in either ubuntu or xp via VirtualBox, and the device, when calling >fastboot devices shows up as ?????????? (ubuntu) and ? (xp)... :\
yellowumbrella said:
yup, that's exactly it.
Haven't tried installing Gapps since I can't even get the rom to boot.
I have a perfectly working tablet with foliomod 1.4, and I did get honeycomb to run but some apps crashed so I reverted back to foliomod.
with CWM CWM 5.5.0.4 everything seems to work great, except at reboot, nothing happens (somehow, I no longer even get the magic value mismatch)
------------------
PS. not sure if this is at all relevant, but I cannot fastboot from win7, I'm fastbooting in either ubuntu or xp via VirtualBox, and the device, when calling >fastboot devices shows up as ?????????? (ubuntu) and ? (xp)... :\
Click to expand...
Click to collapse
Try to install gapps as well. Maybe it helps...
nope, no luck even with gapps installed..
just a blank screen..
sigh
yellowumbrella said:
nope, no luck even with gapps installed..
just a blank screen..
sigh
Click to expand...
Click to collapse
Have you tried all the roms? ICS Alpha 1,2,3 and 4?
Tried 3 and 4, didn't bother trying earlier ones, as it seems the latest ones work for most users
yellowumbrella said:
nope, no luck even with gapps installed..
just a blank screen..
sigh
Click to expand...
Click to collapse
Hmmm strange. I ask it for you on developers forum. What you can still do, is to check the steps, that you did them correctly. In most of the cases users forget something, or do some steps incorrectly.
Try to erase userdata, cache, system, linux and recovery in fastboot. You mentioned you had problem with fastboot under Win7. Problem may occur, in case of not proper erasing.
Thanks, I'll give it another try tonight.
Fastboot in win7 is simply not seeing the device. It shows up in XP and Ubuntu, but as "??????" - not sure if that could be a symptom.
I'll post a reply as soon as I've tried, and let you know how it went.
yellowumbrella said:
Thanks, I'll give it another try tonight.
Fastboot in win7 is simply not seeing the device. It shows up in XP and Ubuntu, but as "??????" - not sure if that could be a symptom.
I'll post a reply as soon as I've tried, and let you know how it went.
Click to expand...
Click to collapse
For me it works perfectly on Win7. After Installing SDK and JDK the in the devicemanager it is shown as an Unknown device. Simply add the driver manually to it.
Download driver from attachment.
Copy it to SDK\USB_driver folder
That works for me. After its done, the Folio is shown as "Fastboot" in device manager. But connect the tablet in fastboot mode to your PC before you add driver manually to it.
Thanks for that.
Tried it, still not working in win7. It shows up correctly in device manager, but fastboot itself just doesn't want to see it...
I've attached a screenshot for you
EDIT: screenshot gets resized, but it shows device manager listing
NVIDIA Android Fastboot Device
and a terminal with fastboot not seeing the device
yellowumbrella said:
Thanks for that.
Tried it, still not working in win7. It shows up correctly in device manager, but fastboot itself just doesn't want to see it...
I've attached a screenshot for you
EDIT: screenshot gets resized, but it shows device manager listing
NVIDIA Android Fastboot Device
and a terminal with fastboot not seeing the device
Click to expand...
Click to collapse
When You have win7, You have run the console as admin!
Or copy the complete Fastboot folder to another Destination like c:\temp...
Thanks stefannsv, tried it, still not showing...
But I can access fastboot on another platform, so I assume it's not an issue, I can just switch over to another OS to flash
no go, followed both this original post (tried all steps except orange, cause the rom I'm trying to install has a system folder, not a system.img)
Last method I tried was:
1) boot into fastboot
2) boot cwm-recovery-5.5.0.4.img directly from PC
3) wipe data/factory reset
4) wipe cache partition
5) install zip from SD card and chose the alpha 4 release
installing update...
then back to recovery, reboot and voilĂ ... magic value mismatch again (it had disappeared for a while... )
Also, when booting into CWM 3.0.0.5, I get a series of "E: Can't mount/cache/recovery" type errors.. could this be related?
booting directly into recovery from PC doesn't alllow me to install any ROMS, not even foliomod 1.4 which works if using puppet13th's method

No Files on SD - ADB Push

After trying to flash AndroWook using Goo Manager, I managed to become stuck in the boot animation. I've tried fastbooting stock system blobs, with no good results. I flashed CWM over TWRP, but CWM can't find any files on my SD. Now I'm trying to ADB push a blobfile (using these directions http://forum.xda-developers.com/showpost.php?p=25216525&postcount=23), but I'm not finding my device.
Can anyone please help me out? I'm so tired of my bricked Prime. There has to be some way that I can be able to flash a ROM onto this thing.
If you have a ROM in a blobbed format, then try the following, as you apparently can connect to your TFP via fastboot:
fastboot -i 0x0b05 flash staging BlobbedRomThatYouAreLoading
This should be similar to the method you used in flashing CWM over TWRP, except you're flashing to the staging partition instead of the recovery partition. On reboot, your ROM should install and load.
A lot of users seem to be having problems connecting to TFP over ADB when in CWM. I'd personally stick with TWRP, as it seems more stable.
Edit:
If the above doesn't work, then I would try flashing TWRP again, then while in TWRP, see if you can connect via ADB. If ADB is still not recognizing your device, then please see this thread and try re-installing your ADB drivers using there:
http://forum.xda-developers.com/showthread.php?t=1426502
kokopuphz said:
If you have a ROM in a blobbed format, then try the following, as you apparently can connect to your TFP via fastboot:
fastboot -i 0x0b05 flash staging BlobbedRomThatYouAreLoading
This should be similar to the method you used in flashing CWM over TWRP, except you're flashing to the staging partition instead of the recovery partition. On reboot, your ROM should install and load.
A lot of users seem to be having problems connecting to TFP over ADB when in CWM. I'd personally stick with TWRP, as it seems more stable.
Edit:
If the above doesn't work, then I would try flashing TWRP again, then while in TWRP, see if you can connect via ADB. If ADB is still not recognizing your device, then please see this thread and try re-installing your ADB drivers using there:
http://forum.xda-developers.com/showthread.php?t=1426502
Click to expand...
Click to collapse
been here done this, install the universal naked drivers first.... then install twrp since it seems to work better then cwm.... then adb push a small file to see of it actually works then push rom and install....
I've got this working up until I try to push something. Pushing something fails because of a "Read only file system."
How do I get my prime to be read/write?
You should fastboot flash twrp, boot to recovery, fixpermissions, then push the rom
Sent from my Transformer Prime TF201 using xda premium
Fixing permissions from TWRP did not help.
im just getting told that fastboot is a not a recognised command which seems like a nooby outcome

[HELP] unlocked bootloader, rooted, and stuck on recovery!

Hello
i managed to unlock my bootloader, flashed twrp recovery, flashed super user.
Tried to install dirty unicorn and got status 7 error.
And now i dont have a rom/os installed.
I tried to move over .zip files through twrp but cant mount drives.
Any help?!?
I TRIED TO PUSH ZIP WITH SIDELOAD AND NO LUCK
BUMP!
i really need to get this fixed please help
xr1charxx said:
BUMP!
i really need to get this fixed please help
Click to expand...
Click to collapse
I did the same thing yesterday, as it was my first time using TWRP (always been a CWM guy), All you have to do to fix it is go into advanced and go into adb sideload, put your rom in you adb folder and run this command
adb sideload nameofzip.zip
Then the zip will be placed in internal storage named sideload.zip and you can flash it.
dsf767 said:
I did the same thing yesterday, as it was my first time using TWRP (always been a CWM guy), All you have to do to fix it is go into advanced and go into adb sideload, put your rom in you adb folder and run this command
adb sideload nameofzip.zip
Then the zip will be placed in internal storage named sideload.zip and you can flash it.
Click to expand...
Click to collapse
Already tried this. when i run adb devices my device does not show up. and when i try to sideload any files i get error:closed
xr1charxx said:
Already tried this. when i run adb devices my device does not show up. and when i try to sideload any files i get error:closed
Click to expand...
Click to collapse
I would try to plug in the USB after your already in recovery.
If you cant get that to work you can always buy this:
https://shopmeenova.appspot.com/st/order.html
its a microusb to microsd its a good worst case and will get you up and running.
do you still have the rom that errored out on you on your internal storage? if so you can always try a fresh wipe and try to install again.

OPX | CM13 | TWRP cannot find zip files and update

I installed SultanXDA's CM13 ROM and I am using TWRP (not the 3 version). I haven't installed SuperSU, so it means that I am not rooted, too... But...
I wanted to flash this camera: http://forum.xda-developers.com/one...t-oxygenos-3-0-1-beta-camera-cm-aosp-t3386799
The problem is that when I get to recovery mode in order to install the zip file, I see all kinds of folders, but not my "normal" ones... I am using my SD card as internal space...
I read somewhere that I have to update to new TWRP 3 in order to overcome this...
So, does it have to do with the version of twrp and if so, how can I update it without being root and without being able for the current TWRP to read the zip files that I will "feed" it?
Maybe my only method is through adb?
Flashing through adb will erase anything else other than changing the TWRP version?
Thanks in advance guys!
dimxr said:
Maybe my only method is through adb?
Flashing through adb will erase anything else other than changing the TWRP version?
Thanks in advance guys!
Click to expand...
Click to collapse
If your Bootloader is unlocked try Fastboot.
Reboot OPX into Fastboot Mode. (Power + Volume Up i think or trough TWRP or CM)
Connect it to your PC
On PC: Download the latest TWRP img File
Start CMD in same Folder as the downloaded File is.
Type: 'Fastboot devices' to make sure your OPX connected properly
Typ: 'Fastboot Flash Recovery *DownloadedTWRP*.img'
Flashing new TWRP only overwrites current TWRP and doesn't erease anything else
OverBit said:
On PC: Download the latest TWRP img File
Click to expand...
Click to collapse
Can you download it?
I can't seem to be able to start a download no matter which browser I use...
dimxr said:
Can you download it?
I can't seem to be able to start a download no matter which browser I use...
Click to expand...
Click to collapse
Without any problem.
Maybe you be able to download it when i attach it.
Was to big to upload it as img, so I renamed it to .apk,
So don't forget to rename it to .img
Great! So, the procedure begins!

Device not recognised in fastboot.

I was trying to install TWRP on my NX529J.
"Adb reboot bootloader command" is working but when i try to install TWRP with command "Fastboot flash recovery recovery.img", it dosent work.
It shows "waiting for devices"
Tried " fastboot devices" NO device there
I tried updating all drivers installed fastboot drivers and zte drivers but still no device found.
In developer settings OEM unlock, USB debugging is on.
and adb mode is also on with *#7678#.
Plz Help.
teji007 said:
I was trying to install TWRP on my NX529J.
"Adb reboot bootloader command" is working but when i try to install TWRP with command "Fastboot flash recovery recovery.img", it dosent work.
It shows "waiting for devices"
Tried " fastboot devices" NO device there
I tried updating all drivers installed fastboot drivers and zte drivers but still no device found.
In developer settings OEM unlock, USB debugging is on.
and adb mode is also on with *#7678#.
Plz Help.
Click to expand...
Click to collapse
sudo fastboot -i 0x19d2 boot recovery.img
sudo command not recognized in windows
anish.mvj said:
sudo fastboot -i 0x19d2 boot recovery.img
Click to expand...
Click to collapse
Sir.
i tried this command also but windows didnt recognized sudo command.
Plz any other way?
teji007 said:
Sir.
i tried this command also but windows didnt recognized sudo command.
Plz any other way?
Click to expand...
Click to collapse
That is ubuntu command.
For windows run CMD as administrator and then run
fastboot -i 0x19d2 boot recovery.img
Thanks and a little more help
anish.mvj said:
That is ubuntu command.
For windows run CMD as administrator and then run
fastboot -i 0x19d2 boot recovery.img
Click to expand...
Click to collapse
Thank you very much
Sir i upgraded my nx529j to 6.0.1, is there anyway to root it or downgrade to 5.1.1?
teji007 said:
Thank you very much
Sir i upgraded my nx529j to 6.0.1, is there anyway to root it or downgrade to 5.1.1?
Click to expand...
Click to collapse
Yes its possible.
Rooting is absolutely not required.
Follow the steps below
1. Download the latest 1.40 firmware from nubia india website support page. [Direct Link]
2. Then open the zip file and extract the recovery.img to local folder. Transfer the zip as it is to SD card
3. Goto fastboot/bootloader and run following
Code:
fastboot -i 0x19d2 flash recovery recovery.img
4. Then select reboot to recovery from bootloader menu.
5. Select wipe all application
6. Then install the downloaded zip [i hope you have already know how to do that]
It will automatically reboot.
That's it you are done downgrading
Failed
anish.mvj said:
Yes its possible.
Rooting is absolutely not required.
Follow the steps below
1. Download the latest 1.40 firmware from nubia india website support page. [Direct Link]
2. Then open the zip file and extract the recovery.img to local folder. Transfer the zip as it is to SD card
3. Goto fastboot/bootloader and run following
Code:
fastboot -i 0x19d2 flash recovery recovery.img
4. Then select reboot to recovery from bootloader menu.
5. Select wipe all application
6. Then install the downloaded zip [i hope you have already know how to do that]
It will automatically reboot.
That's it you are done downgrading
Click to expand...
Click to collapse
It says wiping failed(please wipe again or do it after reboot) everytime.
and nothing is working even app wipe or data wipe, only cache wiped works and choose from phone storage is also n ot working and sd card is also being not dtetected.
even in TWRP
anish.mvj said:
Yes its possible.
Rooting is absolutely not required.
Follow the steps below
1. Download the latest 1.40 firmware from nubia india website support page. [Direct Link]
2. Then open the zip file and extract the recovery.img to local folder. Transfer the zip as it is to SD card
3. Goto fastboot/bootloader and run following
Code:
fastboot -i 0x19d2 flash recovery recovery.img
4. Then select reboot to recovery from bootloader menu.
5. Select wipe all application
6. Then install the downloaded zip [i hope you have already know how to do that]
It will automatically reboot.
That's it you are done downgrading
Click to expand...
Click to collapse
I insatlled TWRP recovery, even in that wiping is not working. is there any way to install custom roms without rooting.
i actully installed official 6.0.1 update from their official nubia site and installed it.
teji007 said:
I insatlled TWRP recovery, even in that wiping is not working. is there any way to install custom roms without rooting.
i actully installed official 6.0.1 update from their official nubia site and installed it.
Click to expand...
Click to collapse
Dude please be clear what you want to do? Stock rom or custom?
Custom
anish.mvj said:
Dude please be clear what you want to do? Stock rom or custom?
Click to expand...
Click to collapse
.
Sir i want custom Rom. and sir now i am bricked
teji007 said:
.
Sir i want custom Rom. and sir now i am bricked
Click to expand...
Click to collapse
what do you mean by your are bricked?
If you want custom rom
Goto TWRP wipe everything
if above fails then try out following
Option 1:
Goto Bootloader mode and from that menu goto emergency recovery. Try wiping from there if successful, flash a stock rom [Kitkat] and boot to system. After first boot goto settings and reset factory settings. Then goto TWRP and wipe, it will wipe for sure. then you can install any custom rom
Option 2:
Download the oldest firmware from the nubia site [1.37] and flash recovery from there [extract the recovery from zip and flash it in bootloader]. Then use
Code:
fastboot -i 0x19d2 boot TWRP.img
to boot to twrp, don't flash it. Then goto advanced and select adb sideload. swipe to start sideload. after that open the zip you downloaded and got to
Code:
/META-INF/com/google/android/
and open updater-script with any of the text file. Delete the first line and save. update the zip.
open cmd from that folder where zip is located. then type
Code:
adb sideload NX529J_Z69_EN_NSXPK1JD00K137.zip
and press enter. let it complete and then reboot. it should boot to factory firmware. Follow the same procedure to factory reset from settings menu then flash TWRP and flash custom rom
Use the above steps. If all fails then revert back.
Thanks going to try
anish.mvj said:
what do you mean by your are bricked?
If you want custom rom
Goto TWRP wipe everything
if above fails then try out following
Option 1:
Goto Bootloader mode and from that menu goto emergency recovery. Try wiping from there if successful, flash a stock rom [Kitkat] and boot to system. After first boot goto settings and reset factory settings. Then goto TWRP and wipe, it will wipe for sure. then you can install any custom rom
Option 2:
Download the oldest firmware from the nubia site [1.37] and flash recovery from there [extract the recovery from zip and flash it in bootloader]. Then use
Code:
fastboot -i 0x19d2 boot TWRP.img
to boot to twrp, don't flash it. Then goto advanced and select adb sideload. swipe to start sideload. after that open the zip you downloaded and got to
Code:
/META-INF/com/google/android/
and open updater-script with any of the text file. Delete the first line and save. update the zip.
open cmd from that folder where zip is located. then type
Code:
adb sideload NX529J_Z69_EN_NSXPK1JD00K137.zip
and press enter. let it complete and then reboot. it should boot to factory firmware. Follow the same procedure to factory reset from settings menu then flash TWRP and flash custom rom
Use the above steps. If all fails then revert back.
Click to expand...
Click to collapse
Thank you very much sir.
Can i contact you by any other means? whatsapp or any other
teji007 said:
Thank you very much sir.
Can i contact you by any other means? whatsapp or any other
Click to expand...
Click to collapse
Check your private message
adb sideload not working
anish.mvj said:
what do you mean by your are bricked?
If you want custom rom
Goto TWRP wipe everything
if above fails then try out following
Option 1:
Goto Bootloader mode and from that menu goto emergency recovery. Try wiping from there if successful, flash a stock rom [Kitkat] and boot to system. After first boot goto settings and reset factory settings. Then goto TWRP and wipe, it will wipe for sure. then you can install any custom rom
Option 2:
Download the oldest firmware from the nubia site [1.37] and flash recovery from there [extract the recovery from zip and flash it in bootloader]. Then use
Code:
fastboot -i 0x19d2 boot TWRP.img
to boot to twrp, don't flash it. Then goto advanced and select adb sideload. swipe to start sideload. after that open the zip you downloaded and got to
Code:
/META-INF/com/google/android/
and open updater-script with any of the text file. Delete the first line and save. update the zip.
open cmd from that folder where zip is located. then type
Code:
adb sideload NX529J_Z69_EN_NSXPK1JD00K137.zip
and press enter. let it complete and then reboot. it should boot to factory firmware. Follow the same procedure to factory reset from settings menu then flash TWRP and flash custom rom
Use the above steps. If all fails then revert back.
Click to expand...
Click to collapse
Sir, its been 5 mins its "starting ADB sideload feature" but nothing
adb sideload failed
anish.mvj said:
Check your private message
Click to expand...
Click to collapse
Sir ,
ADB sideload failed
teji007 said:
Sir ,
ADB sideload failed
Click to expand...
Click to collapse
Hi how did your device visible in fastboot devices?
I installed adb drivers and all but my device is not listed in fastboot devices..
It is being listed in adb devices but not on fastboot devices. Can you help me with this?
---------- Post added at 08:51 PM ---------- Previous post was at 08:50 PM ----------
teji007 said:
I was trying to install TWRP on my NX529J.
"Adb reboot bootloader command" is working but when i try to install TWRP with command "Fastboot flash recovery recovery.img", it dosent work.
It shows "waiting for devices"
Tried " fastboot devices" NO device there
I tried updating all drivers installed fastboot drivers and zte drivers but still no device found.
In developer settings OEM unlock, USB debugging is on.
and adb mode is also on with *#7678#.
Plz Help.
Click to expand...
Click to collapse
Hi how did your device visible in fastboot devices?
I installed adb drivers and all but my device is not listed in fastboot devices..
It is being listed in adb devices but not on fastboot devices. Can you help me with this?

Categories

Resources