A lot of dual sim users complain that their phone doesn't boot after installing cwm. I think this is caused by cwm wiping the misc partition. This is based on this post in the ultimate thread.
It is however not a very practical solution, since you have to do every time you access cwm. Instead I tried to prevent cwm from wiping your misc partition, by outcommenting the misc partition in the fstab file.
But, since I don't have don't have the dual sim model, I need someone (experienced, who knows how to fix a bootloop) to test if it works.
I need someone with a filled in misc partition (when entering fastboot, the OS- must be filled in), hboot 1.03 who won't freak out if the phone bootloops.
Multiple people confirmed that it works. I think you can safely try it, but still: everything at your own risk.
Steps:
1. Make sure you have filled in misc partition. This can be done by flashing a firmware.zip, check part 2 of this post: http://forum.xda-developers.com/showpost.php?p=53901933&postcount=6
2. Install the cwm image from below
3. check if the bootup problem is fixed, and check if you have other problems
Cwm_no_misc_wipe.img (hboot 1.03)
https://www.dropbox.com/s/g8g06wi5ipiw9cb/recovery_cwm_no_misc.img?dl=0(hboot 1.02 and below)
Hmm, would flashing the ZIP from the post you linked be enough to fix the /misc partition, so that I can test your CWM? (I'm not afraid of a boot loop as long as I can still go into fastboot)
Bogdacutu said:
Hmm, would flashing the ZIP from the post you linked be enough to fix the /misc partition, so that I can test your CWM? (I'm not afraid of a boot loop as long as I can still go into fastboot)
Click to expand...
Click to collapse
Yes that would be enough, you do however need to be S-off
I don't have s-off
Sent from my HTC Desire 500 dual sim using Tapatalk
Okay, I got the ZIP from the post you linked and installed the recovery from the first post, it works perfectly now (no more issues with booting after power off). Thanks!
Bogdacutu said:
Okay, I got the ZIP from the post you linked and installed the recovery from the first post, it works perfectly now (no more issues with booting after power off). Thanks!
Click to expand...
Click to collapse
Good!
Hope it also fixes for people who's phone barely boots at all.
For this recovery "cwm_no_misc_wipe .img" do i have to be s-off?
kiddoo said:
For this recovery "cwm_no_misc_wipe .img" do i have to be s-off?
Click to expand...
Click to collapse
Not for the recovery.
Just make sure you have a filled in misc partition, else it won't do anything.
I flashed this new recovery and I noticed any difference (seems not working: I still have the same problem after I turn my phone off (power it off); I still have to remove the battery, wait about 15 minutes, put battery back and then I my phone starts normally). Maybe the reason is wiped this misc partition? How can I check it and - if it be needed - repair it?
dummie999 said:
Not for the recovery.
Just make sure you have a filled in misc partition, else it won't do anything.
Click to expand...
Click to collapse
it's a dual sim with unlocked bootloader. didn't trried anything else everything else is stock. is it filled or....?
the OS part is filled with htc release version 1,26,401,2
Ok.
Installed this recovery, SU and ultimate kernel 8 no oc and everything is ok. The phone boots normally. Thank you very much.
I flashed TWRP with unlocked bootloder and its a dual sim with latest software update. So I flashed TWRP and it booted to TWRP but without touch working or any response so i removed the battery and now phone dosent boot up to anything and just a orange led flashes when connected to charger.. I can't even boot to fastboot or Hboot
OK!!!
Great job, it works! Thanks a lot...
Battery got fully discharged phone wont boot
dummie999 said:
A lot of dual sim users complain that their phone doesn't boot after installing cwm. I think this is caused by cwm wiping the misc partition. This is based on this post in the ultimate thread.
It is however not a very practical solution, since you have to do every time you access cwm. Instead I tried to prevent cwm from wiping your misc partition, by outcommenting the misc partition in the fstab file.
But, since I don't have don't have the dual sim model, I need someone (experienced, who knows how to fix a bootloop) to test if it works.
I need someone with a filled in misc partition (when entering fastboot, the OS- must be filled in), hboot 1.03 who won't freak out if the phone bootloops.
Steps:
1. Make sure you have filled in misc partition
2. Install the cwm image from below
3. check if the bootup problem is fixed, and check if you have other problems
Cwm_no_misc_wipe.img (hboot 1.03)
Click to expand...
Click to collapse
It works thanks very much but there is one problem suddenly while i was hanging out i forgot to charge battery and battery was fully discharged..I was lucky that i had in my pocket my secondary symbian nokia and i put my sim into it..When i returned home i connected phone to charge but orange led blinks i charged it about 30min then i used steps to turn on with previous cwm recovery pulling out batt for 10sec and putting back but phone wont boot after waiting 15 min with this cwm no misc..?Plz help
a small question
THANKS A LOT FOR YOUR WORK BUT CAN I KNOW WHAT DID YOU MEAN IN
1-Make sure you have filled in misc partition
would you please explaine this step because i falshed the recovery image normally and nothing change so i think that this is the problem
sensation199290 said:
THANKS A LOT FOR YOUR WORK BUT CAN I KNOW WHAT DID YOU MEAN IN
1-Make sure you have filled in misc partition
would you please explaine this step because i falshed the recovery image normally and nothing change so i think that this is the problem
Click to expand...
Click to collapse
it would be a lot simpler if you actually read the first post (and the two after it), I bet that's what everyone else who has issues now didn't do too.
Bogdacutu said:
it would be a lot simpler if you actually read the first post (and the two after it), I bet that's what everyone else who has issues now didn't do too.
Click to expand...
Click to collapse
i did it and every thing is alright so thanks again it was a huge problem
Hi
My English is poor.
"1. Make sure you have filled in misc partition."
Do mean the misc partition, is the device internal memory ?
Thank you
farzad130 said:
Hi
My English is poor.
"1. Make sure you have filled in misc partition."
Do mean the misc partition, is the device internal memory ?
Thank you
Click to expand...
Click to collapse
The misc partition is stored on you internal memory, yes.
dummie999 said:
A lot of dual sim users complain that their phone doesn't boot after installing cwm. I think this is caused by cwm wiping the misc partition. This is based on this post in the ultimate thread.
It is however not a very practical solution, since you have to do every time you access cwm. Instead I tried to prevent cwm from wiping your misc partition, by outcommenting the misc partition in the fstab file.
But, since I don't have don't have the dual sim model, I need someone (experienced, who knows how to fix a bootloop) to test if it works.
I need someone with a filled in misc partition (when entering fastboot, the OS- must be filled in), hboot 1.03 who won't freak out if the phone bootloops.
Multiple people confirmed that it works. I think you can safely try it, but still: everything at your own risk.
Steps:
1. Make sure you have filled in misc partition. This can be done by flashing a firmware.zip, check part 2 of this post: http://forum.xda-developers.com/showpost.php?p=53901933&postcount=6
2. Install the cwm image from below
3. check if the bootup problem is fixed, and check if you have other problems
Cwm_no_misc_wipe.img (hboot 1.03)
https://www.dropbox.com/s/g8g06wi5ipiw9cb/recovery_cwm_no_misc.img?dl=0(hboot 1.02 and below)
Click to expand...
Click to collapse
didn't fix it on z4dug
Related
Code:
Use at your own risk. I'm not responsible for bricked devices,
or other things that go wrong
TWRP for the HTC Desire 500 :highfive:
As far as I know, it only works for one sim (z4u), but it might as well work for dual sim (z4dug)
People reported it to work on dual sim.
More info about TWRP here: http://teamw.in/project/twrp2
How to install:
Unlock your bootloader at http://www.htcdev.com/bootloader/
Download https://www.dropbox.com/s/k8iovf93oycip1e/recovery.img
Install fastboot
Open cmdline
cd to the folder where you saved the recovery.img
boot your phone into fastboot mode
type: fastboot flash recovery recovery.img
reboot
Click to expand...
Click to collapse
Many thanks to galaxyfreak, for fixing the bumping recovery screen
Tested:
Full backup&restore
Flash kangbang kernel r3 (http://forum.xda-developers.com/showthread.php?t=2600294)
Changelog:
v1:
Initial build
Yes it was that easy
reserved
dual?
Does this work on dual sim? And if it does could you include tested software version ?
I don't know, because nobody tested it, and I only have one SIM. But I'm quite sure it works, and if it doesn't, nothing could go wrong.
Edit: The software version doesn't matter, if it works for 1.20 it will work for all versions.
I can confirm that it's working on dual SIM device. Until now I have any issues. I have 1.13.401.2 software version.
Desire 500 Dual Sim (z4dug)
eexter said:
I can confirm that it's working on dual SIM device. Until now I have any issues. I have 1.13.401.2 software version.
Click to expand...
Click to collapse
Hi i'm very happy that twrp work with Desire 500 DS (z4dug).
wich method you use to root.
Thanks .
http://forum.xda-developers.com/showthread.php?t=2600294
1. Download the kernel and superuser zip, and save them on you sdcard
2. Mount /system. (under Mount)
3. Flash the kernel (under Install)
4. Flash the superuser (same)
@emosat
I answered your PM right now, but I see dummie was faster
eexter said:
@emosat
I answered your PM right now, but I see dummie was faster
Click to expand...
Click to collapse
:good:
Thanks i hope this is tested on dual sim version.I saw many dead devices
Wait. I have an issue... It restarts my phone during making of backup. I tried to make a backup of boot, data, android_secure and system partitions. It made backup of boot, data, android_secure and their md5 checksums, but after, during making of backup system partition, the phone restarts and boot to system.
eexter said:
Wait. I have an issue... It restarts my phone during making of backup. I tried to make a backup of boot, data, android_secure and system partitions. It made backup of boot, data, android_secure and their md5 checksums, but after, during making of backup system partition, the phone restarts and boot to system.
Click to expand...
Click to collapse
Same problem here, plus I can't use the mount device option, I can select the partitions but then I don't have any button to do it !!!
bricenott said:
Same problem here, plus I can't use the mount device option, I can select the partitions but then I don't have any button to do it !!!
Click to expand...
Click to collapse
ok i'll wait for good "recovery":good:
Thanks a lot.
I had the same problem with the cwm image. When it was backupping android_secure, it suddenly rebooted. I don't know how to fix, will use adb logcat
dummie999 said:
Code:
Use at your own risk. I'm not responsible for bricked devices,
or other things that go wrong
TWRP for the HTC Desire 500 :highfive:
As far as I know, it only works for one sim (z4u), but it might as well work for dual sim (z4dug)
People reported it to work on dual sim.
More info about TWRP here: http://teamw.in/project/twrp2
How to install:
Many thanks to galaxyfreak, for fixing the bumping recovery screen
Tested:
Full backup&restore
Flash kangbang kernel r3 (http://forum.xda-developers.com/showthread.php?t=2600294)
Changelog:
v1:
Initial build
Yes it was that easy
Click to expand...
Click to collapse
Bang!! my device is bricked. It's a dual sim version and is not booting up in neither fastboot nor os even pc isn't detecting the phone. onle led is blinking if I connect the phone with a charger with or without battery. Service center guys asked around 8500 Indian rupees nearly about 145USD for replacing the motherboard. It's totally frustrating you know. Any suggestion ?? By the way I'm from India and I can't even the the right stock rom and kernel for the device,It's carrier free version.
dummie999 said:
Code:
Use at your own risk. I'm not responsible for bricked devices,
or other things that go wrong
TWRP for the HTC Desire 500 :highfive:
As far as I know, it only works for one sim (z4u), but it might as well work for dual sim (z4dug)
People reported it to work on dual sim.
More info about TWRP here: http://teamw.in/project/twrp2
How to install:
Many thanks to galaxyfreak, for fixing the bumping recovery screen
Tested:
Full backup&restore
Flash kangbang kernel r3 (http://forum.xda-developers.com/showthread.php?t=2600294)
Changelog:
v1:
Initial build
Yes it was that easy
Click to expand...
Click to collapse
where is the TWRP 2.7 ?
I flashed your link but is the 2.6.3.0 and have a problem when the phone is shut down and I plug the charger , the recovery start and touch not work; i must take off the battey and reboot.
lupak5 said:
where is the TWRP 2.7 ?
I flashed your link but is the 2.6.3.0 and have a problem when the phone is shut down and I plug the charger , the recovery start and touch not work; i must take off the battey and reboot.
Click to expand...
Click to collapse
I don't know why it isn't twrp 2.7, I downloaded this from the 2.7 branch
About the plugging, well the same problem exists with cwm, I will see if I can fix it
Hi,
is anything happening for the TWRP here or is the work on the recovery stopped??
manne48 said:
Hi,
is anything happening for the TWRP here or is the work on the recovery stopped??
Click to expand...
Click to collapse
Is there anything you miss? yes, basically the work here has stopped, but that is because everything is working, except for adb, but idk how to fix that
bricked..?
I flashed this with unlocked bootloder and its a dual sim with latest software update. So I flashed TWRP and it booted to TWRP but without touch working or any response so i removed the battery and now phone dosent boot up to anything and just a orange led flashes when connected to charger.. Someone please help me
Hi,
It is a pity that it for this phone not a real recovery exist.To less interest in development.
What's there makes problems and do not run properly,i´m a little disappointed and i thought that there is more development; even Android 5, LP
sry for englisch
cheers
manne
HI.
On my rooted 3t i had:
- TWRP 3.0.4-1
- firmware 4.0.3
- ROM RR-N-v5.8.1-20170211
Everything was working great.
I was going through my email when screen went black...
I was not able to turn it on since.
I tried boot to recovery - after few seconds on TWRP flash screen it's not going nowhere... Screen is black and only notification light is white.
Same result when when just starting it.. I see Oneplus logo (powered by Android) and that is it.
Tried to boot into recovery through fastboot with the same result.
Anyone has an idea?
Thank you.
From what you're saying I see that at least the device interacts somehow. Therefore I would suggest trying this --> https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
...no matter how weird and unlucky your situation is
If that won't work then it may be that the Internal memory corrupted
Seems like something went wrong with your internal hardware components. However, try to boot the phone into fastboot mode and try to flash new ROM zip from there with your laptop/pc.
motherninja said:
Seems like something went wrong with your internal hardware components. However, try to boot the phone into fastboot mode and try to flash new ROM zip from there with your laptop/pc.
Click to expand...
Click to collapse
Thank you for responding...
My feeling is the same... Something wrong with hardware.
I did re flash TWRP. TWRP is not loading...
I did try to load TWRP through fastload - same result.
I can (and I think I will) try to flash new ROM but I do not think this would help when even TWRP is not working.
Anyone knows what is warranty situation in my case?
Thank you.
I had the same issue.
Use the unbrick tool. This will help you.
Your problem has nothing to do with hardware.
timobayl said:
I had the same issue.
Use the unbrick tool. This will help you.
Your problem has nothing to do with hardware.
Click to expand...
Click to collapse
Just wondering..
In case of sucessfull unbrick... Does phone would need to be rooted again?
I mean the result is like phone is in original/new state...?
Yes, the phone is like new from the box.
Oos 3.5.4
timobayl said:
Yes, the phone is like new from the box.
Oos 3.5.4
Click to expand...
Click to collapse
The other question is where to go from here... after it is alive again..
What caused that?
Should I go back to
- TWRP 3.0.4-1
- firmware 4.0.3
- latest ROM RR-N-v5.8.1
Thanks
Yes.
For me it works that way.
Maybe its a saver way ota oos Update to 4.0.3.
Than twrp...
TWRP 3.0.4-1 is not restoring internal storage
It is alive...
I ran unbrick tool... and it worked.
Oneplus 3t up and running..
One issue.. TWRP 3.0.4-1 is not restoring DATA completely.
It is showing "Data (excl. storage)" instead of "Data" and not not restoring internal storage (pictures, messages, files).
Anyone knows what to do?
It is the same as before. Nandroid never Backuped the internal storage.
The new twrp show this message to make it ckear for everyone.
What do you think how big is a Nandroid with internal storage?
When I initially went to unlock the bootloader, I encountered an issue, which I did not record anywhere. (Don't remember what it was.) In the end, I was able to update the recovery to the newest available version used here. I could install the Lineage OS roms and I did, except the internal memory was decreased to something like 600mb.
I don't remember what I did from there, but I think I tried to load a scatter file over and flash that. Evidently I barely have a grip on what I'm discussing. I would like to salvage this phone. Its currently showing 0mb for internal storage. Not sure how I can flash a rom over that.
I need to fix the partitioning, but I don't know how and I don't know what to do. Please help. The bootloader is unlocked and not secure.
razz0z said:
When I initially went to unlock the bootloader, I encountered an issue, which I did not record anywhere. (Don't remember what it was.) In the end, I was able to update the recovery to the newest available version used here. I could install the Lineage OS roms and I did, except the internal memory was decreased to something like 600mb.
I don't remember what I did from there, but I think I tried to load a scatter file over and flash that. Evidently I barely have a grip on what I'm discussing. I would like to salvage this phone. Its currently showing 0mb for internal storage. Not sure how I can flash a rom over that.
I need to fix the partitioning, but I don't know how and I don't know what to do. Please help. The bootloader is unlocked and not secure.
Click to expand...
Click to collapse
I have had similar issue , with loosing use of internal storage, normally , on my other devices it could be fixed by doing "format data" either in fastboot or twtp. But I found that sometimes that is not working. What I did , and what I suggest you to try, is to fastboot boot stock-recovery.img, then do factory reset.
mrmazak said:
I have had similar issue , with loosing use of internal storage, normally , on my other devices it could be fixed by doing "format data" either in fastboot or twtp. But I found that sometimes that is not working. What I did , and what I suggest you to try, is to fastboot boot stock-recovery.img, then do factory reset.
Click to expand...
Click to collapse
I don't think I can format the data partition right now, but I will check and try that as soon as the phone charges again. I've been trying and sort of giving up, because I have a lot to learn about the basics before I can actually fix anything without any help. Fastboot mode and then how do I boot the stock-recovery.img? Where do I get that?
Do you mean from a stock rom? Should I allow TWRP to enable read-only mode, because I think it said that it may overwrite TWRP with the stock recovery? Sorry for the ignorance, I'm trying to figure out what I can without help, but I've never been this deep. I've always managed to do these things correctly in the past, without having an extensive understanding of the filesystem or what a kernel is or a bootloader.
Thanks for replying, thanks for your work on the roms here too, by the way.
razz0z said:
I don't think I can format the data partition right now, but I will check and try that as soon as the phone charges again. I've been trying and sort of giving up, because I have a lot to learn about the basics before I can actually fix anything without any help. Fastboot mode and then how do I boot the stock-recovery.img? Where do I get that?
Do you mean from a stock rom? Should I allow TWRP to enable read-only mode, because I think it said that it may overwrite TWRP with the stock recovery? Sorry for the ignorance, I'm trying to figure out what I can without help, but I've never been this deep. I've always managed to do these things correctly in the past, without having an extensive understanding of the filesystem or what a kernel is or a bootloader.
Thanks for replying, thanks for your work on the roms here too, by the way.
Click to expand...
Click to collapse
Use the stock recovery linked in this linked thread.
https://forum.xda-developers.com/showpost.php?p=73290731&postcount=8
there is also directions in the same linked thread , few posts down on how to fastboot boot recovery image.
once booted, try to do factory reset, hopefully it formats your data partition for you.
I am on stock rom, rooted with magisk, and I cannot seem to get this phone decrypted. Every time I try to format data in twrp, I get an error, and I get stuck in a bootloop to recovery. Is there a step(s) I am missing here? I've tried looking through the forum but all I've seen are the same instructions on formatting data.
Use Advanced Wipe, select all except sdcard. Then flash any custom rom you like. Flash Magisk too. Reboot. After reboot try running your custom rom os for a few. Then go back to twrp, do it again advanced wipe except sdcard. Reboot. See if it decrypt now.
Note: Make sure you backup everything in it first before doing so. Goodluck
Sent from my XT1805 using Tapatalk
jdesignz said:
Use Advanced Wipe, select all except sdcard. Then flash any custom rom you like. Flash Magisk too. Reboot. After reboot try running your custom rom os for a few. Then go back to twrp, do it again advanced wipe except sdcard. Reboot. See if it decrypt now.
Note: Make sure you backup everything in it first before doing so. Goodluck
Sent from my XT1805 using Tapatalk
Click to expand...
Click to collapse
Well, I tried it, it booted, but it doesnt detect my sim card, and I have no service. I am still not decrypted as well, I am afraid to format data because of the fact that in the past it has put me into a recovery bootloop.
L4ndon said:
Well, I tried it, it booted, but it doesnt detect my sim card, and I have no service. I am still not decrypted as well, I am afraid to format data because of the fact that in the past it has put me into a recovery bootloop.
Click to expand...
Click to collapse
UPDATE:
I tried to redo the process again, just to verify the process, and I am still having the same network issues. I have 3g every once in a while, but its iffy and I no longer have LTE.
L4ndon said:
Well, I tried it, it booted, but it doesnt detect my sim card, and I have no service. I am still not decrypted as well, I am afraid to format data because of the fact that in the past it has put me into a recovery bootloop.
Click to expand...
Click to collapse
1 - forget the instructions given by the other kid - all wrong (like a lot, if not most, of the info given in theg5s plus threads.
2 - use twrp r15 - found in the forums, I think 16 is listed but I know 15 works. You must boot to twrp once after installing twrp or it'll get replaced with stock.
3 - you must format data to decrypt. Wiping only removes data - not the encryption
4 - I've never used magisk, but pretty sure it removed the encrypting flags when installed. I use su and no problems with stock - I've done it and know it works.
5 - download stock firmware, to fix booting to recovery you'll need stock recovery, and it's handy to have just in case.
What to do - install above twrp recovery - format data partition - install su - reboot. Done. If it is rebooting to recovery (which it shouldn't as long as you do boot to recovery after installing it) - flash stock recovery, reboot normally, then do the twrp install routine again.
Report back with details. No details - no help.
Phazmos said:
1 - forget the instructions given by the other kid - all wrong (like a lot, if not most, of the info given in theg5s plus threads.
2 - use twrp r15 - found in the forums, I think 16 is listed but I know 15 works. You must boot to twrp once after installing twrp or it'll get replaced with stock.
3 - you must format data to decrypt. Wiping only removes data - not the encryption
4 - I've never used magisk, but pretty sure it removed the encrypting flags when installed. I use su and no problems with stock - I've done it and know it works.
5 - download stock firmware, to fix booting to recovery you'll need stock recovery, and it's handy to have just in case.
What to do - install above twrp recovery - format data partition - install su - reboot. Done. If it is rebooting to recovery (which it shouldn't as long as you do boot to recovery after installing it) - flash stock recovery, reboot normally, then do the twrp install routine again.
Report back with details. No details - no help.
Click to expand...
Click to collapse
IT WORKED! Thank you so much. This was the post I needed, it really helps when everything is put in a step by step format, I am not the best when it comes to this stuff, the only reason I wanted a custom rom was to be able to use wifi tether, being on sprint makes that hard. But now that i have the first step down hopefully everything else goes this smooth. Thank you so much again!
Well, as long as you have done backup with twrp you have nothing to worry about.
Sent from my XT1805 using Tapatalk
L4ndon said:
IT WORKED! Thank you so much. This was the post I needed, it really helps when everything is put in a step by step format, I am not the best when it comes to this stuff, the only reason I wanted a custom rom was to be able to use wifi tether, being on sprint makes that hard. But now that i have the first step down hopefully everything else goes this smooth. Thank you so much again!
Click to expand...
Click to collapse
Doing things the right way always works! Trouble is finding that right way (heed my warning about bad info in these threads - there is a lot of it - as you found out). Just so happens I also know how to splain things to users, I've done it for something like 25+ years (yeah, I am old - make that experienced). Tethering - used to be ya add a build.prop entry to allow it, but that was many years ago and most of not all enable it by default now.
Anyways, enjoy the ride. It may be a little bumpy, but it's the bumps that keep ya awake!
Phazmos said:
1 - forget the instructions given by the other kid - all wrong (like a lot, if not most, of the info given in theg5s plus threads.
2 - use twrp r15 - found in the forums, I think 16 is listed but I know 15 works. You must boot to twrp once after installing twrp or it'll get replaced with stock.
3 - you must format data to decrypt. Wiping only removes data - not the encryption
4 - I've never used magisk, but pretty sure it removed the encrypting flags when installed. I use su and no problems with stock - I've done it and know it works.
5 - download stock firmware, to fix booting to recovery you'll need stock recovery, and it's handy to have just in case.
What to do - install above twrp recovery - format data partition - install su - reboot. Done. If it is rebooting to recovery (which it shouldn't as long as you do boot to recovery after installing it) - flash stock recovery, reboot normally, then do the twrp install routine again.
Report back with details. No details - no help.
Click to expand...
Click to collapse
THX for that, got stuck in recovery process (loop).
I followed your instructions, but need of stock recovery.
My Path :
Backup DATA (w/o /media/)
Manually Backup Media with TWRP to Ext.SD
FORMAT /Data (use the DATA Button in TWRP), in my case it showed Errors, i ignored it and did it once again - this time it worked.
flashed Magisk
ended up in Recovery Loop - flashed stock recov. via FASTBOOT, reboot
a rainbow lightning circle turned up, said " DELETING", device rebooted by itself.
Now the Phone boots to Android, shut it down, restart with PWR BUTOON + VOL DOWN pressed to access bootloader and flash twrp again with FASTBOOT ( fastboot flash recovery nameoftheimage.img ENTER).
Now u can restore /DATA TWRP Backup and then the manually part - in my case that worked.
THX!
//EDIT
After first boot, i noticed missing write permissions for most Apps - so i decided to Reset SELinux via TWRP, worked !
te amo hice format data con r15 y al parecer se soluciono todo son lo maximo cauros
Phazmos said:
1 - forget the instructions given by the other kid - all wrong (like a lot, if not most, of the info given in theg5s plus threads.
2 - use twrp r15 - found in the forums, I think 16 is listed but I know 15 works. You must boot to twrp once after installing twrp or it'll get replaced with stock.
3 - you must format data to decrypt. Wiping only removes data - not the encryption
4 - I've never used magisk, but pretty sure it removed the encrypting flags when installed. I use su and no problems with stock - I've done it and know it works.
5 - download stock firmware, to fix booting to recovery you'll need stock recovery, and it's handy to have just in case.
What to do - install above twrp recovery - format data partition - install su - reboot. Done. If it is rebooting to recovery (which it shouldn't as long as you do boot to recovery after installing it) - flash stock recovery, reboot normally, then do the twrp install routine again.
Report back with details. No details - no help.
Click to expand...
Click to collapse
still sim not showing on my device which is xt1804
Never had the problem so can't help.
heya people! my razer 2 is screwed. I had trinity kernel originally, and i saw arter's was updated to april and trinity was march so i flashed arter's, someone else did it with no issue.
K so i flash arter, go to system, reboot, someone in tg group told me arter is sketchy and known to brick phones, so i wanted to go back to trinity, before tho, someone said i should clean flash my stock, so i tried. The thing is, the file comes from razer, and is a flash_all.bat the only problem was i couldnt use fastboot, so after talking to them i tried to just flash the boot.img to boot slot in twrp. Big mistake. Twrp no longer is a thing, fastboot doesnt work, cant go into download mode, when i boot up my phone it tells me my phone is corrupted and may not function, after that it takes me to default android recovery screen.
if i hit apply via adb, i get sys errors and **** and according to nfs group, my partition is completely corrupted (device not found) or something like that
so i called a repair place and explained it to him and he said hed have to look at it, so im gonna probably have to drive down there for him to tell me its screwed.
I tried applying via sd card, but when i insert the sdcard to my pc and try to write files, it says its write protected, and i dont see anything in properties about making it r/w so im really at a loss.
Is there ANYTHING i can do or am i gonna have to pray that this guy knows something?
dont thikn i can send to razer since i broke my warranty unlocking bootloader and rooting.
anything would help guys, i dont wanna have to go back to my razer 1 ;_;
ok well i didnt get any replies so i took it to a repair place, he said his tech guy wasnt in but he'd call me with updates as to whats happening. Shouldnt cost more than $75 so thats great.
if you have any ideas on what could be wrong id love to hear, maybe i can learn from my mistakes and be able to recover next time.
I'm not sure about the comments in the telegram group, but I don't think it was necessary to flash all the stock stuffs. Factory images may contain stuffs that you should never flash on a device that has already left factory and packaged. Usually you should only be flashing boot, system and vendor (plus userdata, if you want to wipe existing data as well). You may also consider flashing modem, dsp, bluetooth if baseband/firmware update on certain parts are needed.
Recovery is now part of the kernel image, so flashing stock kernel means you have stock recovery. Stock recovery is only useful if you accidentally issued Factory Reset from system, or pressed "Wipe user data" from bootloader (which happened when I was preparing the device for unlock/rooting for the first time), and got into an endless loop after that (since TWRP may not properly handle /misc stuffs).
Again, **NEVER** use Factory Reset from system, or Wipe user data from bootloader, if you use TWRP. Always wipe data from TWRP if you intend to do so.
At one point (r13) arter97's kernel had some issues which is supposed to have been fixed in r14. I haven't updated my kernel yet since last Trinity nightly (it's working great even after flashing MR3 vendor stuffs).
LSS4181 said:
I'm not sure about the comments in the telegram group, but I don't think it was necessary to flash all the stock stuffs. Factory images may contain stuffs that you should never flash on a device that has already left factory and packaged. Usually you should only be flashing boot, system and vendor (plus userdata, if you want to wipe existing data as well). You may also consider flashing modem, dsp, bluetooth if baseband/firmware update on certain parts are needed.
Recovery is now part of the kernel image, so flashing stock kernel means you have stock recovery. Stock recovery is only useful if you accidentally issued Factory Reset from system, or pressed "Wipe user data" from bootloader (which happened when I was preparing the device for unlock/rooting for the first time), and got into an endless loop after that (since TWRP may not properly handle /misc stuffs).
Again, **NEVER** use Factory Reset from system, or Wipe user data from bootloader, if you use TWRP. Always wipe data from TWRP if you intend to do so.
At one point (r13) arter97's kernel had some issues which is supposed to have been fixed in r14. I haven't updated my kernel yet since last Trinity nightly (it's working great even after flashing MR3 vendor stuffs).
Click to expand...
Click to collapse
hmm, im not understanding how flashing stock boot.img to boot partition would make recovery part of the kernel image? boot.img is the literal only thing i got to flash in twrp before it just died.
Like i said fastboot didnt work, and oddly enough, it doesnt work on my old razer 1 either, i tried rooting it the other day and it wont go to fastboot
Edit: according to an admin in magnetar group, dm-verity could be the reason, and he said i should've flashed something called "lazy flasher" after flashing the boot img. Never heard of it and never used it.
hadtosignuptoreply said:
hmm, im not understanding how flashing stock boot.img to boot partition would make recovery part of the kernel image? boot.img is the literal only thing i got to flash in twrp before it just died.
Like i said fastboot didnt work, and oddly enough, it doesnt work on my old razer 1 either, i tried rooting it the other day and it wont go to fastboot
Edit: according to an admin in magnetar group, dm-verity could be the reason, and he said i should've flashed something called "lazy flasher" after flashing the boot img. Never heard of it and never used it.
Click to expand...
Click to collapse
Recovery is built into the kernel (which is common for recent devices). arter97 (or Trinity) kernel image includes TWRP in place of the stock recovery, so you get TWRP when you flashed the kernel. Stock boot.img comes with stock recovery, so if you flash stock kernel you lose TWRP.
Also, keep track of your reboot count and your current active slot. If your system fails to boot multiple times in a row, the bootloader may consider it damaged and switching to another slot (which usually contains the previous version of system/vendor/modem etc.) and may cause some issues if you're unlocked (or you were previously on a GSI).
As for fastboot issues, I once had a time that I could only conduct flash commands within a very tiny time window right after the phone booted to bootloader, although the problem has been lessened after reboot and I could now flash properly again. It's unknown when the problem would resurface that I'd need another reboot (given the distro I use, Manjaro, is constantly updating, I'd just update the system and reboot anyway if that happens).
Some fastboot versions may be buggy, or maybe USB interactions under Linux can be problematic in general (especially in handling plugs and unplugs). This is more apparent if a system is running constantly for a long time and a lot of devices has been properly (or improperly) plugged or unplugged over the course of its uptime. Maybe it's better if one conducts fastboot using rear USB ports (as front USB ports tend to have less voltage).
I never bothered with dm-verity and hardly ever had problems with it.
vnb
LSS4181 said:
Recovery is built into the kernel (which is common for recent devices). arter97 (or Trinity) kernel image includes TWRP in place of the stock recovery, so you get TWRP when you flashed the kernel. Stock boot.img comes with stock recovery, so if you flash stock kernel you lose TWRP.
Also, keep track of your reboot count and your current active slot. If your system fails to boot multiple times in a row, the bootloader may consider it damaged and switching to another slot (which usually contains the previous version of system/vendor/modem etc.) and may cause some issues if you're unlocked (or you were previously on a GSI).
As for fastboot issues, I once had a time that I could only conduct flash commands within a very tiny time window right after the phone booted to bootloader, although the problem has been lessened after reboot and I could now flash properly again. It's unknown when the problem would resurface that I'd need another reboot (given the distro I use, Manjaro, is constantly updating, I'd just update the system and reboot anyway if that happens).
Some fastboot versions may be buggy, or maybe USB interactions under Linux can be problematic in general (especially in handling plugs and unplugs). This is more apparent if a system is running constantly for a long time and a lot of devices has been properly (or improperly) plugged or unplugged over the course of its uptime. Maybe it's better if one conducts fastboot using rear USB ports (as front USB ports tend to have less voltage).
I never bothered with dm-verity and hardly ever had problems with it.
Click to expand...
Click to collapse
ah ok. Well the repair guy called and said they didnt know what was wrong or how to fix it, i know i can at least get to bootloader, and to root my razer 1 again, i went to bootloader and fastboot worked. Before work tomorrow im gonna get that phone from the place and hope that i can flash what i need to get it working again. Assuming it will actually be able to read the device. Thanks for your input