Hey, look what i've done while desperately trying to install GearCM or CM12 ROM. First, i installed TWRP on my i9500 device. After that, i put the GearCM 5.1 and Gapps for 5.1 on sdcard, but i got mad really fast when i saw i can't install ANY ZIP from sdcard, then tried another CUSTOM ROMS, same problem, i wiped cache and system ( ye, system ) ) - dont ask why i did that - Anyway, now i have no system files on phone, and on my sdcard i only got that useless ZIPs.
Ah, forgot to mention, the error showing up everytime i tried to install a zip was : "Zip corrupted, Operation aborted" (something like that ).
NOTE : I can't boot normally, but i can boot in recovery (TWRP) . I can't flash another rom using odin as i can't switch usb debugging ON.
Ah, please, don't laugh too much, im pretty serious
Oh, some1 explain this to me -> I tried to install zip @ adb as i saw explained on a blog -> got stuck at recognizing phone-pc due to driver error, so i decided to try last time installing the custom ROMs( THE SAME ZIPs i got error before) from recovery -> install zips. AND GUESS WHAT, less than 20s rom is installed without any errors, i dont know if to be mad or happy. Atleast explain me what happened there.
wowempire said:
Hey, look what i've done while desperately trying to install GearCM or CM12 ROM. First, i installed TWRP on my i9500 device. After that, i put the GearCM 5.1 and Gapps for 5.1 on sdcard, but i got mad really fast when i saw i can't install ANY ZIP from sdcard, then tried another CUSTOM ROMS, same problem, i wiped cache and system ( ye, system ) ) - dont ask why i did that - Anyway, now i have no system files on phone, and on my sdcard i only got that useless ZIPs.
Ah, forgot to mention, the error showing up everytime i tried to install a zip was : "Zip corrupted, Operation aborted" (something like that ).
NOTE : I can't boot normally, but i can boot in recovery (TWRP) . I can't flash another rom using odin as i can't switch usb debugging ON.
Ah, please, don't laugh too much, im pretty serious
Click to expand...
Click to collapse
*stare and laughing a lot*
*Just kidding, okay? :silly: *
And then;
You have corrupted zips. You need to redownload the package completely (ROM+GApps) and transfer it to your external SD card and flash. You can transfer the downloaded zips by using adb push command or remove your external SD card and plug it to anything else (read: SD card reader; of course ).
Sent from my ASUS_Z00AD
krasCGQ said:
*stare and laughing a lot*
*Just kidding, okay? :silly: *
And then;
You have corrupted zips. You need to redownload the package completely (ROM+GApps) and transfer it to your external SD card and flash. You can transfer the downloaded zips by using adb push command or remove your external SD card and plug it to anything else (read: SD card reader; of course ).
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
Yeah, maybe im not exactly as n00b as you think. I used exactly the same zips after(same procedure tho), and it worked smooth(i didn'teven touch them).
NOTE : I think i said i tried using adb to install zips but i got a driver error which i couldn't solve.
I've had that issue for some time especially with CM, have you tried verifying the sh1 checksum once you've loaded it onto your sd card?
Thanks.
Related
I wanted to flash PSX Pure Speed Experiment 4.4 rom but I got the " Failed. E:Error executing updated binary in zip '/sdcard/psx_mako_kk_v1..." message mentioned in the OP. I tried the solution posted there, which was to download a patched multirom version of TWRP recovery using the flashify app from the play store. This all seemed to work out fine, and I booted into recovery to flash the rom. Now, this could just be due to my ignorance because the version of TWRP I flashed is 2.6.3.2 (I originally had 2.3.0.1 I believe), but when I wiped my phone, then went to install, there wasnt anything listed in the root of my sd card folder. I tried rebooting TWRP and when I tried again it listed a folder named TWRP there but nothing else. Subsequent reboots yielded nothing. At this point I dont even want to flash the 4.4 rom, I just want to reflash my old CM10.1 rom and be done with it. Any help is greatly appreciated
sropedia said:
I wanted to flash PSX Pure Speed Experiment 4.4 rom but I got the " Failed. E:Error executing updated binary in zip '/sdcard/psx_mako_kk_v1..." message mentioned in the OP. I tried the solution posted there, which was to download a patched multirom version of TWRP recovery using the flashify app from the play store. This all seemed to work out fine, and I booted into recovery to flash the rom. Now, this could just be due to my ignorance because the version of TWRP I flashed is 2.6.3.2 (I originally had 2.3.0.1 I believe), but when I wiped my phone, then went to install, there wasnt anything listed in the root of my sd card folder. I tried rebooting TWRP and when I tried again it listed a folder named TWRP there but nothing else. Subsequent reboots yielded nothing. At this point I dont even want to flash the 4.4 rom, I just want to reflash my old CM10.1 rom and be done with it. Any help is greatly appreciated
Click to expand...
Click to collapse
Reboot the phone and then connect it to your PC and check to see if the PSX ROM file is there. If not, redownload the file and save it in the root of the SDcard. As for the TWRP folder that has nothing in it, delete it. Then try to boot into recovery and flash the PSX ROM, also just making sure that the checkbox for "System" in mount section is unchecked. BTW, is your a multiROM patch for TWRP?
taodan said:
Reboot the phone and then connect it to your PC and check to see if the PSX ROM file is there. If not, redownload the file and save it in the root of the SDcard. As for the TWRP folder that has nothing in it, delete it. Then try to boot into recovery and flash the PSX ROM, also just making sure that the checkbox for "System" in mount section is unchecked. BTW, is your a multiROM patch for TWRP?
Click to expand...
Click to collapse
Thanks for the reply, but when I try to mount my phone, my computer acknowledges that I've connected a device with a sound, but it doesnt show up as a storage device. when I go into devices and printers I can find my phone but it only shows up as an ADB device
And yes to answer your question it is a multiROM patch for TWRP
sropedia said:
Thanks for the reply, but when I try to mount my phone, my computer acknowledges that I've connected a device with a sound, but it doesnt show up as a storage device. when I go into devices and printers I can find my phone but it only shows up as an ADB device
Click to expand...
Click to collapse
Do you have "USB debugging" checkbox, in Developer Options, checked? Also, try reboot your PC and reconect your phone to see whether it shows up as a storage device.
sropedia said:
I wanted to flash PSX Pure Speed Experiment 4.4 rom but I got the " Failed. E:Error executing updated binary in zip '/sdcard/psx_mako_kk_v1..." message mentioned in the OP. I tried the solution posted there, which was to download a patched multirom version of TWRP recovery using the flashify app from the play store. This all seemed to work out fine, and I booted into recovery to flash the rom. Now, this could just be due to my ignorance because the version of TWRP I flashed is 2.6.3.2 (I originally had 2.3.0.1 I believe), but when I wiped my phone, then went to install, there wasnt anything listed in the root of my sd card folder. I tried rebooting TWRP and when I tried again it listed a folder named TWRP there but nothing else. Subsequent reboots yielded nothing. At this point I dont even want to flash the 4.4 rom, I just want to reflash my old CM10.1 rom and be done with it. Any help is greatly appreciated
Click to expand...
Click to collapse
ok when you wiped your rom did you just do a factory reset or a internal sd wipe as well. Also you should try and use 2.6.3.3. Also you have to remember where it is you save your stuff or place everything in 1 specific folder. May I suggest you start over with downloading rom and putting it in a folder created by you like !Flash... using "!" will ensure its the first folder you see.
Also your error also can be fixed by simply rebooting your recovery as its been what I used to fix that error
playya said:
ok when you wiped your rom did you just do a factory reset or a internal sd wipe as well. Also you should try and use 2.6.3.3. Also you have to remember where it is you save your stuff or place everything in 1 specific folder. May I suggest you start over with downloading rom and putting it in a folder created by you like !Flash... using "!" will ensure its the first folder you see.
Also your error also can be fixed by simply rebooting your recovery as its been what I used to fix that error
Click to expand...
Click to collapse
I did a full wipe like I usually do. I would use a different version of TWRP if I knew how to change it from within TWRP. I have a follder titled ROOT that I keep all my ROMs and whatnot in, but the problem is that literally none of the folders in my internal storage are showing up from within TWRP. I can't check to see if USB debugging is enabled because theres no operating system on my phone; like I said, I did a full wipe. The fact that no folders show up also means that it doesnt recognize the backup I had. My computer still won't recognize my phone as a storage device after mounting in TWRP. Maybe I'm doing something in the wrong order? Restarting my computer didn't help.I really need to get my phone working on ANY ROM, and I appreciate all the help so far
Hi guys,
I have tried to install to my p700 new kitkat custom rom, but every time i install it, it says: e: cannot write to /sdcard/clockworkmod/.last install_path.....
i have tried to make clockworkmod folder and put rom and GAPPS in there, i have tried, cyanogenmod, prime mod, slimkat and some other i dont remember... i also try not to care about that message and just rebooted to system, but it stays in boot loop.
I am starting to feel this phone hates me because i cannot install anything to this phone, i ever "accidentally" was able to install 4.3 cyanogenmod, but it started to be so laggy and my wife got frustrated with it...
Any ideas?
EDIT: my cwm is latest phillz
Kaafan said:
Hi guys,
I have tried to install to my p700 new kitkat custom rom, but every time i install it, it says: e: cannot write to /sdcard/clockworkmod/.last install_path.....
i have tried to make clockworkmod folder and put rom and GAPPS in there, i have tried, cyanogenmod, prime mod, slimkat and some other i dont remember... i also try not to care about that message and just rebooted to system, but it stays in boot loop.
I am starting to feel this phone hates me because i cannot install anything to this phone, i ever "accidentally" was able to install 4.3 cyanogenmod, but it started to be so laggy and my wife got frustrated with it...
Any ideas?
EDIT: my cwm is latest phillz
Click to expand...
Click to collapse
put rom and gapps in sd card wherever and install, what the **** where you trying to do?
ok, so i have tried to install many different kitkat roms to my p700 but all of those installs ends to an error: e: cannot write to /sdcard/clockworkmod/.last install_path.
If i just ignore that and reboot to system it just stays in boot loop.
edit: after install it say install complete but then there is that error too
Kaafan said:
ok, so i have tried to install many different kitkat roms to my p700 but all of those installs ends to an error: e: cannot write to /sdcard/clockworkmod/.last install_path.
If i just ignore that and reboot to system it just stays in boot loop.
edit: after install it say install complete but then there is that error too
Click to expand...
Click to collapse
uhhh, where do you keep roms? At least answer questins if you want hep. also update cmw to cmw 6.0.4.8 ,yo ucan get in original development thread
Lukijs said:
uhhh, where do you keep roms? At least answer questins if you want hep. also update cmw to cmw 6.0.4.8 ,yo ucan get in original development thread
Click to expand...
Click to collapse
i keep roms and gapps in sd-card, root folder
Kaafan said:
i keep roms and gapps in sd-card, root folder
Click to expand...
Click to collapse
root folder? lol , put them in storage 1 which is external sd card if you have one.
Lukijs said:
root folder? lol , put them in storage 1 which is external sd card if you have one.
Click to expand...
Click to collapse
lol lol, if i speak about internal storage i will say internal storage, if i speak about sd-card that mean sd-card....
and i know how to flash roms, i have latest 4.4.3 in my N7000
my cwm is v6.0.4.7
i just need help, how to solve that error
Kaafan said:
lol lol, if i speak about internal storage i will say internal storage, if i speak about sd-card that mean sd-card....
and i know how to flash roms, i have latest 4.4.3 in my N7000
my cwm is v6.0.4.7
i just need help, how to solve that error
Click to expand...
Click to collapse
http://www.donofweb.com/how-to-solv...xternal-sd-card-in-clockworkmod-cwm-recovery/
i saw that guide before and already forget
the second question is that because i dont own micro-sd reader, is it possible to format to FAT32 in android phone, my n7000 is fine and working so i can do with it, if it is possible, if not then i just have to go buy sd-card reader
thanks for the help Lukijs
Lukijs said:
http://www.donofweb.com/how-to-solv...xternal-sd-card-in-clockworkmod-cwm-recovery/
Click to expand...
Click to collapse
now i have micro-sd adapter and i have formatted it in to a FAT32 and i checked that sd card is primary not logical. But still same problem. any other ideas? :crying:
i just installed new ( 3 days old ) phillz cwm, cwm version number is now 6,0,4,8
Kaafan said:
now i have micro-sd adapter and i have formatted it in to a FAT32 and i checked that sd card is primary not logical. But still same problem. any other ideas? :crying:
i just installed new ( 3 days old ) phillz cwm, cwm version number is now 6,0,4,8
Click to expand...
Click to collapse
try to use CWM 6.0.3.2, I have problems with philz CWM when restoring backup
vinhlinh.nguyen said:
try to use CWM 6.0.3.2, I have problems with philz CWM when restoring backup
Click to expand...
Click to collapse
i already got it working, but now i got new problem
installing many many roms and formatting and clearing everything has destroyed my IMEI, now i just try to find some help how to install my phone imei
Caveat emptor: adopt/follow this guide at your own risk.
Below is a procedure that can be used to update your HD+ EMMC to LN14.1 from CM11 (if your HD+ is currently running stock ROM, use the process described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810/).
Download the following files to a location in your user content-media storage space on the HD+:
amaces' flashable TWRP zip file, e.g., twrp-3.0.1-0-ovation.zip ( https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778)
amaces' flashable LN14.1 ROM zip file, e.g., lnos_ovation-ota-NMF26Q.170104.zip from https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778
the flashable zip file of the Gapps pico package open_gapps-arm-7.1-pico-2017[mmdd].zip from http://opengapps.org/
Boot into your current EMMC recovery.
Select install zip and install the TWRP recovery zip file obtained in step 1(a).
Power off the Nook.
Boot into the new TWRP recovery flashed in the step 3 (press and hold the Home button, then press and hold the Power button until after the CyanoBoot Universal Bootloader screen comes on, then release both buttons).
Select wipe /data & factory reset.
Select install zip and install the LN14.1 zip file.
Select install zip and install the Gapps zip file.
Reboot into the new LN14.1.
Once the Nook completes the boot (be patient as it takes quite a bit of time), set up the Wifi connectivity and your Google account info. Note that the Apps you previously have on CM11 will not be auto-downloaded/restored into your new LN14.1.
If you run into problems during initial setup:
- absence of WiFi network setup step: see this post
- setup process crashes (as have been reported with some combos of ROM and GApps build versions): retry the clean install process with the sequence of steps # 6, #7 & #9 (i.e., skipping over step #8 flashing GApps) and complete the initial setup, then reboot into TWRP to flash GApps; see also https://forum.xda-developers.com/showpost.php?p=72104906&postcount=37 for solution for other setup crash causes.
To enable "Root", see https://forum.xda-developers.com/showpost.php?p=72185622&postcount=1915.
Notes
If you encounter errors in step 3 (using your existing CWM recovery to flash the new TWRP zip file):
- If you have a SD card handy, consider using the procedure described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
- Otherwise, you can try to flash the flashable TWRP zip file available at http://www.mediafire.com/file/3gj4g9j1x363dor/cwm-flashable_twrp-3.0.1-0-ovation.zip.
Please post any comment/question on the features or performance of AOSP & LN ROM builds on the Developer's thread at https://forum.xda-developers.com/nook-hd/development/marshmallow-nook-hd-hd-t3239269.
I'm on CM11 and am getting hung up trying to install TWRP. I get:
This package is for device: ovation; this device is .
Status 7
Installation aborted
Tips?
I'm running EMMC CWM v6.0.4.6
stupid_nut said:
I'm on CM11 and am getting hung up trying to install TWRP. I get:
This package is for device: ovation; this device is .
Status 7
Installation aborted
Tips?
I'm running EMMC CWM v6.0.4.6
Click to expand...
Click to collapse
Is your device a Nook HD+?
digixmax said:
Is your device a Nook HD+?
Click to expand...
Click to collapse
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
stupid_nut said:
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
Click to expand...
Click to collapse
Have you tried flashing TWRP through their official app? I think I also had trouble trying to flash TWRP through CWM, but the app worked at the time.
You could also flash internal TWRP through Amaces's multi mode bootable SD recovery. It does mean you'd need to setup a spare SD card for it, but it can be good to have handy anyway [emoji6]
stupid_nut said:
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
Click to expand...
Click to collapse
I can't tell why the update script doesn't identify your device as "ovation".
If you have an SD card handy, I'd suggest that you try the procedure described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810. Otherwise, you can try to flash the flashable TWRP zip file available at http://www.mediafire.com/file/3gj4g9j1x363dor/cwm-flashable_twrp-3.0.1-0-ovation.zip.
Thanks guys!
I just ended up using the SD card procedure. TWRP app failed as well. CM11 was slowing to a crawl on the NookHD+ so hopefully Lineage will give it new life!
error 20 on gapps (you don't have Android 7)
Hi, had CM11 on my HD+ for over a year. Unfortunately I left it on til battery completely discharged the other night, and even after charging to 100%, it would only go in a boot loop. (cyanogenmod bootloader, then robot face, then cyanogenmod bootloader again, then robot face again, etc, nonstop). So I thought, why not wipe it and put Lineage on?
So first following the link from this thread, for doing a from scratch install (not the link for if you have CM11 since it wasn't even booting for me, so assuming corrupt),
I got to the point of installing TWRP, and it failed with a zip signature verification error. So okay, I uncheck that verification box, and it appeared to install okay. Onto the lnos zip file. As a precaution, I also unchecked the verification box (thinking it might fail like the TWRP install), and besides a couple messages about "E: unknown command [LOG] " which I ignored (from what I read online can be safely ignored?) , and it took a good while (10 or more minutes? didn't time it) and says "script succeeded: result was [10000000] ,updating partition details, ....done" So I assumed it installed? Then tried installing open_gapps-arm-7.1-pico-20170329.zip, and it fails with "This GApps pkg is for Android 7.1.X only. Please download the correct version for your ROM: 4.4.4.(SDK 19) GApps installation failed No changes were made to your device. Installer will now exit Error Code: 20" and install failed basically. So I reboot and what do you know I still see the CM boot loop going on. Does this mean the old CM11 OS is still installed? Or just a bootloader? And if I press "N" I see TWRP as an option, as well as CM (legacy) So I boot to TWRP and go to Wipe, but this time, do Advanced, and select to wipe all items except external SD. Restart, and same CM boot loop is going on. (I had done the basic Wipe before that)
So something isn't right here, or I'm missing some steps? Any help please?
baytee said:
...
So something isn't right here, or I'm missing some steps? Any help please?
Click to expand...
Click to collapse
Since you're posting in this thread, I can't tell if you have tried the alternative procedure in this thread https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
digixmax said:
Since you're posting in this thread, I can't tell if you have tried the alternative procedure in this thread https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
Click to expand...
Click to collapse
YES I tried both procedures. In fact I tried that link you have for "installing new" procedure first But it failed on the Gapps part. And like I said the previous CM11 (at least boot part) seems corrupt as its stuck in a boot loop. So ideally if it's not riskier, I was attempting to wipe off the old system. (unless by checking all the boxes except SD, under Wipe, Advanced, I did accomplish that? and just the boot/bootloader portion remains?
baytee said:
...
So first following the link from this thread, for doing a from scratch install (not the link for if you have CM11 since it wasn't even booting for me, so assuming corrupt),
I got to the point of installing TWRP, and it failed with a zip signature verification error. So okay, I uncheck that verification box, and it appeared to install okay. Onto the lnos zip file. As a precaution, I also unchecked the verification box (thinking it might fail like the TWRP install), and besides a couple messages about "E: unknown command [LOG] " which I ignored (from what I read online can be safely ignored?) , and it took a good while (10 or more minutes? didn't time it) and says "script succeeded: result was [10000000] ,updating partition details, ....done" So I assumed it installed? Then tried installing open_gapps-arm-7.1-pico-20170329.zip, and it fails with "This GApps pkg is for Android 7.1.X only. Please download the correct version for your ROM: 4.4.4.(SDK 19) GApps installation failed No changes were made to your device. Installer will now exit Error Code: 20" and install failed basically. So I reboot and what do you know I still see the CM boot loop going on. Does this mean the old CM11 OS is still installed? Or just a bootloader?
Click to expand...
Click to collapse
It appears that the old CM11 ROM is still there, the "... succeed ... " message notwithstanding.
The problem behavior seems to be pointing to the possibility that your EMMC is hosed (not readable/writeable). You can test this by trying to re-install stock ROM (see #6 of https://forum.xda-developers.com/showthread.php?t=2062613).
And if I press "N" I see TWRP as an option, as well as CM (legacy)
Click to expand...
Click to collapse
These are just the choices of TWRP & CWM recovery available on the SD.
So I boot to TWRP and go to Wipe, but this time, do Advanced, and select to wipe all items except external SD. Restart, and same CM boot loop is going on. (I had done the basic Wipe before that)
...
Click to expand...
Click to collapse
You should never need to wipe anything other than /data and /cache (/system typically gets wiped automatically (aka reformatted) as part of the process of flashing a new ROM version).
digixmax said:
It appears that the old CM11 ROM is still there, the "... succeed ... " message notwithstanding.
The problem behavior seems to be pointing to the possibility that your EMMC is hosed (not readable/writeable). You can test this by trying to re-install stock ROM (see #6 of https://forum.xda-developers.com/showthread.php?t=2062613).
.
Click to expand...
Click to collapse
I downloaded the stock rom zip , put it on sdcard, booted to TWRP, didn't do any Wipe but clicked Install, chose that zip, unchecked zip signature verification, swiped to start it, get:
"Failed to retouch '/system/lib/libemoji.so'.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/NookHDplus-stock-2.1.1.-rooted.zip'
Updating partition details...
...done
So, any hope for my HD+ ? If eMMC IS hosed as you mention, what causes this? And are there any tricks to UN-Hose it? Or is it now a useless dead tablet? Why would my battery going to zero screw things up so badly?
baytee said:
I downloaded the stock rom zip , put it on sdcard, booted to TWRP, didn't do any Wipe but clicked Install, chose that zip, unchecked zip signature verification, swiped to start it, get:
"Failed to retouch '/system/lib/libemoji.so'.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/NookHDplus-stock-2.1.1.-rooted.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
To flash stock ROM you need CWM version 6.0.2.8 attached at the end of the post I referenced.
So, any hope for my HD+? If eMMC IS hosed as you mention, what causes this? And are there any tricks to UN-Hose it? Or is it now a useless dead tablet?
Click to expand...
Click to collapse
If your EMMC is dead, you can try to run CM11 entirely off an SD card -- see https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/.
My Hd is one of those that won't reliably boot to sd card. Any possibility for unbricking , Similar to these (though these steps are for nook tablet, not HD)?
https://forum.xda-developers.com/showthread.php?t=1513583http://bishoptec.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
baytee said:
My Hd is one of those that won't reliably boot to sd card. Any possibility for unbricking , Similar to these (though these steps are for nook tablet, not HD)?
https://forum.xda-developers.com/showthread.php?t=1513583http://bishoptec.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Click to expand...
Click to collapse
That "tool" for unbricking the NT also boots and runs off a SD card.
While it never reliably booted to the cm11 OS on the sdcard, it's been booting okay lately to recovery at least Twrp maybe even cwm , so assuming I can boot to those , again,does that repair option for NT also work for HD+?
baytee said:
While it never reliably booted to the cm11 OS on the sdcard, it's been booting okay lately to recovery at least Twrp maybe even cwm , so assuming I can boot to those , again,does that repair option for NT also work for HD+?
Click to expand...
Click to collapse
The NT unbricking tool only works for the NT.
Assuming your EMMC is not dead, and its factory-installed partition structure is not corrupted or altered, you can accomplish the same end-goal as the NT tool does by re-flashing to stock ROM using the files linked in the post I had referenced in my earlier reply.
digixmax said:
The NT unbricking tool only works for the NT.
Assuming your EMMC is not dead, and its factory-installed partition structure is not corrupted or altered, you can accomplish the same end-goal as the NT tool does by re-flashing to stock ROM using the files linked in the post I had referenced in my earlier reply.
Click to expand...
Click to collapse
Thank you but again , i tried that already and it failed, which is why I was asking if any of those procedures in the links I posted would work, which u already indicated the NT one wouldn't. I've seen various other xda posts talking about either ADB or partitioning or formatting commands. Was just hoping this HD+ wasn't dead and that I could somehow hack this back to life instead of chucking it in the trash....
baytee said:
Thank you but again , i tried that already and it failed, which is why I was asking if any of those procedures in the links I posted would work, which u already indicated the NT one wouldn't. I've seen various other xda posts talking about either ADB or partitioning or formatting commands. Was just hoping this HD+ wasn't dead and that I could somehow hack this back to life instead of chucking it in the trash....
Click to expand...
Click to collapse
The stock rom you tried to install was the rooted version that I customized. Try a plain stock rom from that same thread. Try an older version. That error was a common one for some devices.
Sent from my SM-T707V using XDA Premium HD app
Will this guide also work on the Nook HD? (Using the equivalent Hummingbird files, of course).
Hello all,
I decided to install a recovery mode called Philz touch v6.07.6, which completed successfully and I can access to both download mode and this recovery menu. Then used Kingroot to root the phone. I then tried to use the ADB system to install a ROM due to not having an SD card at the time. I had chosen the option to clean install which deleted cache and formatted certain folders. The installation process then failed and I can only access download mode and recovery and my phone does not connect to my laptop anymore, or any other. I cannot seem to connect my phone to any computer, either with different cables or USB port.
I've uninstalled KIES, smart switch. uninstalled and reinstalled all drivers but my phone still does not connect to Odin or ADB server. I cannot install a new recovery menu as I cannot see my phone on Odin.
Thinking an SD card with a ROM would resolve the issue I purchased a card, added a ROM to it but I cannot find anything I put on the sd card. Choosing install from zip then SD card it shows clockworkmod/ but nothing else. Using free browse mode i've looked into every folder and cannot find anything that is on my SD card. I see no option under mounts and storage to mount the SD card
Thank you for your time and if you can advise me on what I am doing wrong.
Edit: I forgot to mention - When powering the phone on normally without trying to get into recovery or download mode, the top left of the screen says:
"Kernel is not seanandroid enforcing"
Set Warranty Bit : kernel
You do realize the S4 has an internal storage, right? It's a built-in microSD card.
So you absolutely don't need one to use and/or flash custom ROMs on it.
Your second mistake was flashing PhilZ recovery. It's a mistake because that recovery is outdated.
Your third mistake was trying to flash the ROM via ADB when you can simply flash it with the recovery.
The reason why the ROM zip doesn't show up in your recovery id because, most probably, the internal storage is selected by default. So, either navigate to the microSD card folder or move the ROM zip to your internal storage.
I also recommend switching to TWRP recovery.
@Aysta, if it's not too late for you, just flash the latest twrp Recovery ". Tar. File" in Odin (>AP) by switching off the device in download mode. After that just copy your desired custom rom and gapps to your sd-card by an sd-card reader in Windows and the rest you know, which as i assume, will follow... [emoji6]
P. S I just experienced the same yesterday evening when i bricked one of my Sammy's while using an experimental kernel (. Img) file.
Anyhow, this just solved everything for me [emoji4]
Aysta said:
Hello all,
I decided to install a recovery mode called Philz touch v6.07.6, which completed successfully and I can access to both download mode and this recovery menu. Then used Kingroot to root the phone. I then tried to use the ADB system to install a ROM due to not having an SD card at the time. I had chosen the option to clean install which deleted cache and formatted certain folders. The installation process then failed and I can only access download mode and recovery and my phone does not connect to my laptop anymore, or any other. I cannot seem to connect my phone to any computer, either with different cables or USB port.
I've uninstalled KIES, smart switch. uninstalled and reinstalled all drivers but my phone still does not connect to Odin or ADB server. I cannot install a new recovery menu as I cannot see my phone on Odin.
Thinking an SD card with a ROM would resolve the issue I purchased a card, added a ROM to it but I cannot find anything I put on the sd card. Choosing install from zip then SD card it shows clockworkmod/ but nothing else. Using free browse mode i've looked into every folder and cannot find anything that is on my SD card. I see no option under mounts and storage to mount the SD card
Thank you for your time and if you can advise me on what I am doing wrong.
Edit: I forgot to mention - When powering the phone on normally without trying to get into recovery or download mode, the top left of the screen says:
"Kernel is not seanandroid enforcing"
Set Warranty Bit : kernel
Click to expand...
Click to collapse
You have to get your phone working with Odin, it's your only way out.
lekiaM said:
@Aysta, if it's not too late for you, just flash the latest twrp Recovery ". Tar. File" in Odin (>AP) by switching off the device in download mode. After that just copy your desired custom rom and gapps to your sd-card by an sd-card reader in Windows and the rest you know, which as i assume, will follow... [emoji6]
P. S I just experienced the same yesterday evening when i bricked one of my Sammy's while using an experimental kernel (. Img) file.
Anyhow, this just solved everything for me [emoji4]
Click to expand...
Click to collapse
Odin doesn't detect his device, read his full post.
MigoMujahid said:
You have to get your phone working with Odin, it's your only way out.
Odin doesn't detect his device, read his full post.
Click to expand...
Click to collapse
"this doesnt make sense than, either"
And i overlooked it. Can happen mate.
Thank you for your assistance guys, i've still not been able to flash a new recovery as my phone just will not connect. I read installing older drivers helps but it didn't. Older odin didn't work. I need to access an operating system which isn't Windows 10 according to another website. So will create a virtual machine and let you all know how it goes.
Ubuntu has worked! i installed jodin3 and my phone shows up on there while in download mode
lekiaM said:
"this doesnt make sense than, either"
And i overlooked it. Can happen mate.
Click to expand...
Click to collapse
Aysta said:
Ubuntu has worked! i installed jodin3 and my phone shows up on there while in download mode
Click to expand...
Click to collapse
That's why i told you it's the Only way, Odin must detect your phone, otherwise you're screwed.
First of all, I read this thread, but no luck.
Situation:
* I unlocked bootloader, installed TWRP 3.1.1-1 and flashed Freedom OS, succeding.
* Then I decided to try the Oreo open beta, but had a problem (error 7 flashing it), so I wanted to get back to Freedom OS
* After flashing Freedom OS again (with success) I rebooted but I was stuck at boot logo.
* I decided to flash again OOS 4.5.14, but I misclicked something and I found my self in TWRP with no ROM to flash on SDcard (I think I have checked also internal storage while wiping).
* PANIC!
So, 3 questions:
1) given that I want to stay encrypted (if still possible at this point) should I decrypt data or not at TWRP boot?
2) if I chose decrypt with the unlock code (read that I did) I have to go with decrypt or formatting is enough to keep crypt?
3) MORE IMPORTANT: how do I get a ROM to flash into the phone. Reeboting in TWRP sometimes I see the internal storage, but when I drop a firmware in it I get the transfer windows stuck at 0% and it disappear after a few seconds.
Thanks in advance to who will help me!
this might help - https://forum.xda-developers.com/showthread.php?t=2318497
chris4500uk said:
this might help - https://forum.xda-developers.com/showthread.php?t=2318497
Click to expand...
Click to collapse
Thanks for the suggestion and... it's a beginning.
The problem is that if I sideload a small file like Magisk upload is ok, even if (obviously) it can't install.
When it comes to Oxygen OS I get I cannot read file error.
I doubleclicked the file and it opens in PC, so it isn't corrupted.
I'd be tempted to try another USB cable and maybe another computer if you have one. Failing that, if it's a problem with TWRP your last resort may be a complete low level flash. A good guide is here - https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
Edit: I should say be careful if you do have connectivity problems, as flashing using unbrick tools while your connection is bad would not be a good idea at all since it could make things even worse (maybe even hard brick)
I finally got it working. I am a bit ashamed of what the problem was, but I share in case someone else does this stupid error.
The point is: I was formatting /data inside Advanced wipe instead of using "Format Data", so ( I think) I was not rebuilding the sd card allocation table.
After formatting with "Format data" I was able to put the firmware with drag and drop from the PC and I could finally have mu OP5 working again.
Can't you press reboot to recovery and decrypt with your code so your device gets mounted on a PC? Otherwise you can adb sideload the oxygenos file. I had the same error, but Google gave me this:
https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47
Use the program on all the files in the adb directory and reboot.
Zocker1304 said:
Can't you press reboot to recovery and decrypt with your code so your device gets mounted on a PC? Otherwise you can adb sideload the oxygenos file. I had the same error, but Google gave me this:
https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47
Use the program on all the files in the adb directory and reboot.
Click to expand...
Click to collapse
No; i couldn't. But I solved simply by using "Format data".
SOLVED
UncleDan said:
I finally got it working. I am a bit ashamed of what the problem was, but I share in case someone else does this stupid error.
The point is: I was formatting /data inside Advanced wipe instead of using "Format Data", so ( I think) I was not rebuilding the sd card allocation table.
After formatting with "Format data" I was able to put the firmware with drag and drop from the PC and I could finally have mu OP5 working again.
Click to expand...
Click to collapse
Format data is necessary on the OP5 when moving between Nougat and Oreo. I hope you flashed the Oreo Open Beta rather than Freedom. It's far superior.
jhs39 said:
Format data is necessary on the OP5 when moving between Nougat and Oreo. I hope you flashed the Oreo Open Beta rather than Freedom. It's far superior.
Click to expand...
Click to collapse
[O/T ON]
I didn't at the moment, but I did right now, reverting to stock recovery. Do you now if an Oreo-ready TWRP is around yet?
[O/T OFF]
UncleDan said:
[O/T ON]
I didn't at the moment, but I did right now, reverting to stock recovery. Do you now if an Oreo-ready TWRP is around yet?
[O/T OFF]
Click to expand...
Click to collapse
There are two with download links included in the instructions thread for flashing Oreo. I recommend the Blu Spark TWRP over the Chinese TWRP. It will be updated more often.