So, last night I was messing around with some custom roms, and tried installing CM, I accidentally installed CM recovery as the boot img, and tried to backup from my backup file that I created via TWRP.
Now, when restoring i get into a bootloop, i think, and if I'm trying to install a custom ROM i either get a status 7 error or it can mount /system. I tried going into the Mount tab in TWRP and checking the system check-box, but it won't let me.
Help XDA-kenobi, you're my only hope.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ThaBlobFish said:
So, last night I was messing around with some custom roms, and tried installing CM, I accidentally installed CM recovery as the boot img, and tried to backup from my backup file that I created via TWRP.
Now, when restoring i get into a bootloop, i think, and if I'm trying to install a custom ROM i either get a status 7 error or it can mount /system. I tried going into the Mount tab in TWRP and checking the system check-box, but it won't let me.
Help XDA-kenobi, you're my only hope.
Click to expand...
Click to collapse
Flash a factory image and start fresh. And don't flash the wrong img to the wrong partition this time
... Device won't show up when i try to list it in CMD under fastboot devices... makes it knda hard to flash. Maybe I should just stop messing with this ****...
Disregard, I am apparently mentally challenged...
ThaBlobFish said:
... Device won't show up when i try to list it in CMD under fastboot devices... makes it knda hard to flash. Maybe I should just stop messing with this ****...
Disregard, I am apparently mentally challenged...
Click to expand...
Click to collapse
You did not mention that in earlier post. If you can't flash via recovery and can't use fastboot then you are screwed. Take this as an expensive lesson to always triple check what you are flashing.
---------- Post added at 02:04 PM ---------- Previous post was at 01:51 PM ----------
After thought. Have you tried flashing just a boot img from recovery?
XxMORPHEOUSxX said:
You did not mention that in earlier post. If you can't flash via recovery and can't use fastboot then you are screwed. Take this as an expensive lesson to always triple check what you are flashing.
---------- Post added at 02:04 PM ---------- Previous post was at 01:51 PM ----------
After thought. Have you tried flashing just a boot img from recovery?
Click to expand...
Click to collapse
I used an old directory with old files which I used to root my M7, that's why it didn't show up. It's all fixed now.
ThaBlobFish said:
I used an old directory with old files which I used to root my M7, that's why it didn't show up. It's all fixed now.
Click to expand...
Click to collapse
Oh, Good. Glad you figured it out!
Related
in the noob sticky thread in the general form there are several cwm types found-permanent, temporary..etc
which one should i flash?
also permanent can be removed if i flash stock with odin in the future right?
thanks!
PS if it is not too much trouble could you also post the link?
There are only 2 kinds of recoveries for sgy
That is stock and cwm
baically cwm temporapy if flashed via cwm and is automatically removed when u exit recobery mode
Permanant one replaces the stock recovery and u cannot it...
It comes with kernels(most of them) cwm recovery is advaisable cause it offers many options like backup restore and many more
Also many zips (tars in some cases) are only cimpatable with cwm as they use busybox command ... any more quiries ... feel free
Its nice to see u saw an article in general and came back here to post question
Many noobs have made a mess in general and theming :banghead:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
=========HOLO-UBUNTU========theme
CWM provides more features but it works the same with stock,
permanent CWM's are built and integrated into the kernel,
temporary CWM are ones overwrite the current recovery but will be rewritten by kernel during boot.
it does not matter though which one you use unless the rom author specifiacally told you to use CWM
sanny5 said:
There are only 2 kinds of recoveries for sgy
That is stock and cwm
baically cwm temporapy if flashed via cwm and is automatically removed when u exit recobery mode
Permanant one replaces the stock recovery and u cannot it...
It comes with kernels(most of them) cwm recovery is advaisable cause it offers many options like backup restore and many more
Also many zips (tars in some cases) are only cimpatable with cwm as they use busybox command ... any more quiries ... feel free
Its nice to see u saw an article in general and came back here to post question
Many noobs have made a mess in general and theming :banghead:
=========HOLO-UBUNTU========theme
Click to expand...
Click to collapse
okay..now im really confused cant understand anything
so what should i do? flash a kernel? or flash cwm? and could u please please post a link on what to do? (im still in doubt about the earlier question on permanent cwm -can it be removed later?)
please help!
thanks!
Hi all, well I think I have all but fubarred my 16gb shield tv. I unlocked bootloader, installed twrp and rooted, all was working fine. Then I decided to flash the full android rom that is on the forum . before doing so, i used twrp and made a backup. I installed the full android rom, although it seemed to work fine, i was not crazy about it and decided to go back to the original OS, so I booted up in twrp and went to the restore function, there were no backups to restore , I guess when I installed the system img for the full android it erased my backup somehow. anyway, moving right along, I next went to nvidia website and downloaded the restore image for the 16gb shield tv, i booted in to bootloader and was following the instructions to restore the shield. all seems to go fine until I try to flash the system img, then I get the error "invalid sparse file format at unknown block 0000" it tries to continue but fails, afterwards the system will not boot at all, I can get back to twrp recovery an flash the full android rom just fine, but am not able to flash back the original os without that error. any suggestions would be greatly appreciated, as I am stuck at this point as what to attempt next. thanks
Here is an image of the error I get, I am no longer able to write to the system partition,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
cdsn99 said:
Here is an image of the error I get, I am no longer able to write to the system partition
Click to expand...
Click to collapse
Just going to go out on limb here, but are you sure the downloaded image isn't corrupted? You could try to download it again, if available do a MD5 hash check to verify it downloaded correctly and then retry flashing it.
d-dragon said:
Just going to go out on limb here, but are you sure the downloaded image isn't corrupted? You could try to download it again, if available do a MD5 hash check to verify it downloaded correctly and then retry flashing it.
Click to expand...
Click to collapse
thanks d-dragon, I re downloaded the image from nvidia and was able to successfully flash it, thanks for the reply and help
Glad to hear my suggestion helped you out Enjoy the shield!
Sent from my Nexus 5 using Tapatalk
send the link
cdsn99 said:
thanks d-dragon, I re downloaded the image from nvidia and was able to successfully flash it, thanks for the reply and help
Click to expand...
Click to collapse
can send the link for stock rom
ahm3336 said:
can send the link for stock rom
Click to expand...
Click to collapse
https://developer.nvidia.com/gameworksdownload
hello, i just tried to flash cloudyg2 3.3 and i have bricked my d802 16gb. i had stock lp and had rooted and installed twrp did the wipes (no internal), got the right lp bootstack and used the right settings, so i really dont know what went wrong.
the symptom is that lg logo show for a fraction of a second and then a washed out gray on top of screen that fades away slowly. also while connected in pc it reads like many many drives.
on the bright side i can enter recovery/download modes. in my original attempt i used the bumbed sign, on my tries to fix it i also used the loki one, same deal.
seems like i have no recovery file, i thought i did it with one of the programs i installed, but since i am newbie seems like i misunderstood. so no recovery file
any help?
solution found:
1.Download the latest TWRP from blastagator here.
2.Flash it with your current recovery, reboot into that new recovery.
3.Download SRKG2 rom (by somboons) here.
4.This rom is a full stock rom with some debloat and custom camera. Wipe /system/ /cache/ /dalvik-cache/ /data/ and flash it (choose any options, it's not important since you'll be only installing this rom because it also upgrades other partitions to a lollipop supported version.
5.Boot into the rom and reboot into recovery again. (If you are unable to boot or the boot is taking too long like 10 minutes, shut down, go to recovery again and perform a factory reset, the one that makes you type 'yes' in the keyboard and you should be fine).
6.Download CloudyG2 3.1 and wipe /system/ /cache/ /dalvik-cache/ /data/ again.
7.Flash the rom choosing the correct version of your phone (among other preferences) in the aroma installer.
8.Boot and enjoy!
i cant post link of the solution cause i am new, but many thanks to him. i still dont understand what went wrong, but my hypothesis is that i shouldnt install the lp bootloader since i was in lp anyway.
i hope it helps anyone with similar problem.
cheers
you are in qhsusb bulk 9006 souse srktool to unbrick
---------- Post added at 07:22 AM ---------- Previous post was at 07:20 AM ----------
that becuase wrong bootleader u must use bump kk bootleader then reboot recovery and flash rom
Can not change lte to 3g can someone please...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-D800 using Tapatalk
Hi everybody !
because of this problem,I want to reset my P9 lite,to see if it'll help.I wanted to reset from settings,but I have a question :
My p9 lite (VNS-L31 C432B380) has TWRP 3.1.1-1 and the official superSU.If i launch the reset process from settings,will it complete even if I have twrp as recovery,or will it be stuck in the middle (which means soft-brick,bootloop,or whatever :crying: ) ?
EinderJam said:
Hi everybody !
because of this problem,I want to reset my P9 lite,to see if it'll help.I wanted to reset from settings,but I have a question :
My p9 lite (VNS-L31 C432B380) has TWRP 3.1.1-1 and the official superSU.If i launch the reset process from settings,will it complete even if I have twrp as recovery,or will it be stuck in the middle (which means soft-brick,bootloop,or whatever :crying: ) ?
Click to expand...
Click to collapse
You can launch factory reset , no problem. You will lose SuperSu only. And data of course
Thanks ! Supersu is not a problem,I still have the zip I flashed when I rooted my phone.
For the data,hisuite should do the job for backup/restore.
Just to be sure, factory reset won't touch SD card,will it ?
EinderJam said:
Thanks ! Supersu is not a problem,I still have the zip I flashed when I rooted my phone.
For the data,hisuite should do the job for backup/restore.
Just to be sure, factory reset won't touch SD card,will it ?
Click to expand...
Click to collapse
No, but you can remove SD card from phone for sure , or you can unmount it in memory (storage) settings.
---------- Post added at 12:06 ---------- Previous post was at 12:03 ----------
EinderJam said:
Thanks ! Supersu is not a problem,I still have the zip I flashed when I rooted my phone.
For the data,hisuite should do the job for backup/restore.
Just to be sure, factory reset won't touch SD card,will it ?
Click to expand...
Click to collapse
Sorry
bozka1 said:
No, but you can remove SD card from phone for sure , or you can unmount it in memory (storage) settings.
---------- Post added at 12:06 ---------- Previous post was at 12:03 ----------
Sorry
Click to expand...
Click to collapse
Why sorry ?
EinderJam said:
Why sorry ?
Click to expand...
Click to collapse
Sorry for duplicate post .
Sorry,but I'll need your help again ^^
When I hit factory reset under advanced settings/backup and restore,the phone reboots to twrp.Then I reboot to system,and nothing have been deleted.I think I'll need the stock recovery of my build (B380),do you know how where can I find it ?
Edit: Ok,I downloaded the FullOTA-MF package from FF. FF says it's 1.601GB,it downloads a 1.25GB update.zip file and I end with a 2.51GB update.app file.
Using huawei update extractor,I have this :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Which recovery should I extract and flash ? both have the same size
EDIT: I flashed recovery.img (everything went fine). EMUI was asking me to update to B388 for ages,so I downloaded it (362Mo) and tried to install it.The phone rebooted to stock recovery (so I assume it's working) but failed to verify the update package (although it downloaded himself like 2min before).After reboot,it proposes the B388-FULL package in settings,can I install it or am I facing a problem ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well the procedure is the same of MIUI rom, the difference is that i have builded first the rom and after converted it into a Treble AB Image.
1) Flash the firmware .48 Pie, unlock the BL and flash the Pitch Black Recovery
2) Assure that in recovery is unchecked the option "Disable DM Verity", format and wipe data, dalvik and cache and flash this force decryption - DO NOT WIPE SYSTEM OR VENDOR!
3) In the follow order flash first this boot patched for .48, then this system image and after latest Magisk.zip
4) Resize the system partition in the wipe advanced menu and reboot in system. These steps to follow are very important. You will take a bootloop but don't worry!
5) Return in recovery, flash the Permissiver V4 by ErfanAbdi and after reboot in system. New bootloop. Now return again in recovery and use the follow patch. Insert this file (by pitch black file manager) into system/system/etc/permissions (if you don't find this specific path means that don't have followed the steps correctly!) and give to it chmod 755
6) Now, at the next reboot, the rom should boot. Don't flash any zip of gapps, otherwise you will take a new bootloop.
I have realized this rom with ashusharma's trees modified by me and using the latest kernel asus .48 always patched by me, you can build other roms using these sources but remember always to convert the ROM into AB Treble Image with ErfanGSITool and apply the patches for bootloop.
That's all!!!
BUGS
Installation of Gapps or set of any security pattern lock create bootloop at reboot
Great bro, i try
wait i m having issues now....wait that finish to test and update the correct procedure
Ok issues resolved. Follow the guide step by step
fosseperme said:
Ok issues resolved. Follow the guide step by step
Click to expand...
Click to collapse
Thanks for the firmware, the only thing that doesn't work is MTP
---------- Post added at 06:31 AM ---------- Previous post was at 06:08 AM ----------
After installing the firmware, the main screen was not. In the settings I had to turn on gestures. When you open FM-Radio closes with an error
Eolvand said:
Thanks for the firmware, the only thing that doesn't work is MTP
---------- Post added at 06:31 AM ---------- Previous post was at 06:08 AM ----------
After installing the firmware, the main screen was not. In the settings I had to turn on gestures. When you open FM-Radio closes with an error
Click to expand...
Click to collapse
MTP works...you must select the mode usb in developer option
Please make it official
Link is not working