Hey.
i just s-off'd my phone, rooted it and all that fun stuff. Now when i tried to flash [ROM][Sept26][INC S]Virtuous Unity 2.39.0 Sense 3.0 Based on Pyramid. everything went well, until the installation was finished. It just stopped on the bootlogo HTC. and nothing. been this for the last 30 minutes or so. what to do ? can i pull the battery and it might boot up correctly?
EDIT:
okey, pulled the battery, managed to backup and restore. question is, will it work if i try again? hahah- im to afraid to try-
Thanks
Robin
Frantiic said:
Hey.
i just s-off'd my phone, rooted it and all that fun stuff. Now when i tried to flash [ROM][Sept26][INC S]Virtuous Unity 2.39.0 Sense 3.0 Based on Pyramid. everything went well, until the installation was finished. It just stopped on the bootlogo HTC. and nothing. been this for the last 30 minutes or so. what to do ? can i pull the battery and it might boot up correctly?
EDIT:
okey, pulled the battery, managed to backup and restore. question is, will it work if i try again? hahah- im to afraid to try-
Thanks
Robin
Click to expand...
Click to collapse
From recovery mode did you wipe data, cache and dalvik cache before you flashed the ROM? Also which recovery did you install after you S-OFF?
Did you see this note on the Original Post of the ROM:
Important Notes
If you are experiencing random freezes and/or reboots, this is likely due to your device being incapable of handling our overclocking defaults. Download and apply this flashable patch, which will reduce the maximum CPU frequency to 1Ghz and likely eliminate this issue.
You must complete a full wipe prior to installing this ROM the first time. We also recommend wiping between upgrades, but you are welcome to try upgrading without a wipe. However, no support will be provided if you file a bug without having wiped prior to submission.
Also, did you follow all of the steps that were listed in the second post?
thanks for the respons.
I used revolutinory.io to do everything.. i did wipe and all that, but still had the problem. i downloaded the patch in the topic, but how do i install it ? transfer it to my sd card and run it from the phone ? and then flash the rom?
thanks
tpbklake said:
From recovery mode did you wipe data, cache and dalvik cache before you flashed the ROM? Also which recovery did you install after you S-OFF?
Did you see this note on the Original Post of the ROM:
Important Notes
If you are experiencing random freezes and/or reboots, this is likely due to your device being incapable of handling our overclocking defaults. Download and apply this flashable patch, which will reduce the maximum CPU frequency to 1Ghz and likely eliminate this issue.
You must complete a full wipe prior to installing this ROM the first time. We also recommend wiping between upgrades, but you are welcome to try upgrading without a wipe. However, no support will be provided if you file a bug without having wiped prior to submission.
Also, did you follow all of the steps that were listed in the second post?
Click to expand...
Click to collapse
Frantiic said:
thanks for the respons.
I used revolutinory.io to do everything.. i did wipe and all that, but still had the problem. i downloaded the patch in the topic, but how do i install it ? transfer it to my sd card and run it from the phone ? and then flash the rom?
thanks
Click to expand...
Click to collapse
A patch implies that you flash the ROM and then while still in recovery you flash the patch file and then reboot.
tpbklake said:
A patch implies that you flash the ROM and then while still in recovery you flash the patch file and then reboot.
Click to expand...
Click to collapse
yeah, but when im done with the flashing of the rom, the phone stops and i cant go any further .. thats the problem. but i will transfer it to the sd card and try
Frantiic said:
yeah, but when im done with the flashing of the rom, the phone stops and i cant go any further .. thats the problem. but i will transfer it to the sd card and try
Click to expand...
Click to collapse
Some roms auto reboot after flashing.
Pull the battery, then turn phone on by holding power and volume down at same time. Choose bootloader then recovery.
Now you can flash the patch.
scoobysnacks said:
Some roms auto reboot after flashing.
Pull the battery, then turn phone on by holding power and volume down at same time. Choose bootloader then recovery.
Now you can flash the patch.
Click to expand...
Click to collapse
thanks for the respons.
I do that, but when it says "Done" nothing happens. im stuck at the white background and the green hTC logo ..
Allright. After 6 reboots and recoverys and all that kind of jazz, it worked..
Related
Please Help I installed a custum ROM and now I am stuck in a loop a skull comes up and droid and it continues till the battery is dies. I have tried to factory reset and nothing the only way to turn it off is to remove the battery can someone please Help
If the ROM is what's causing the problem, doing a factory reset won't change anything; it'll stil keep the same ROM in place. What you might want to do is download a more popular ROM, like a CM7 nightly, put it on your microSD card (using another phone or a microSD adapter, of course) and boot into recovery and flash that.
If that doesn't work, I dunno then. I got a bootloop the other day after using ROM Manager to flash a new kernel. Turns out it was the kernel because after a factory reset, it booted up fine. So I just chose another kernel and it's all good now.
You just might have a screwy ROM. Try reflashing it if you can. What was the custom ROM, btw?
Yeah I'd agree with the above; install another ROM and make sure to wipe cache and dalvik and if it still doesn't work wipe data as well. Note that wiping data will wipe pretty-much everything on your phones memory (SMS messages, contacts, accounts etc)
when it is cm7 than you should take an other kernel
Please, if you are experiencing random reboots (that involve the M logo) or prolonged screen freezes, you should revert to an older beta kernel that is free of the DSI errors. To do so, replace the boot.img in the update-cm-7...zip package with this one (from 0.04 version): http://code.google.com/p/cyanogenmod4milestone/downloads/detail?name=bootimg0.04.zip
Click to expand...
Click to collapse
Stole that from another Thread:
_Flash with any rom you have
_Milestone will auto reboot after flash done and loop
_Don't worry about that, remove battery in 5s and re-plugin
_Turn on your milestone: hold X and POWER to access Recovery. Select Wipe and reboot
Do you have a Droid or a Milestone? If you have a Milestone, which country is the device from?
I had a boot loop issue too on my UK Milestone when I tried to install CM6.1.2, version 28.01.2011 0.07-11.01.28. (http://android.doshaska.net/cm6)
This is what I did to fix the problem...
- Flashed UK 2.1 SBF file
- Flashed Vulnerability Recovery
- Rooted the phone
- Installed and booted into OpenRecovery
- Installed 15.01.2011 0.06-11.01.15 version (phone booted fine)
- Rebooted into OpenRecovery > Wiped Dalvik Cache
- Applied 28.01.2011 0.07-11.01.28 version
One more thing, you may need to update and/or change your baseband files.
I hope this helps.
Thx for the help guys I,m back up an running. Greatly appreciated
Sent from my Droid using XDA App
Hi all. Yes I am a Noob first ever post in fact. I am however good at following directions and reading first. So far found nothing to address my issue.
Intro: First time flashing a Custom ROM although I did previously successfully install Cf-Root and Stock ICS from Sam Mobile using excellent instructions found here.
Background: 1) Decided to move from Rooted Stock ICS to new Aliance ICS -- spent all weekend reading up before developing courage to attempt. 2) Today Successfully downgraded to Gingerbread (Flashing the Darky Resurrection rom and following instructions exactly). 3) Uninstalled DarkyOTA and Cleared app data as specified in instruction 4) Installed Alliance OTA and ROM Config as specified 3) Successfully flashed a XXLPY repack via ODIN per http://forum.xda-developers.com/showpost.php?p=27199210&postcount=4instructions 5) Copied the Alliance ICS Rom Zip to external SD 6) Went into CWM as instructed and flashed file.
Result: received notices -- Preparing for Installation ... Cleaning the phone etc -- through to "Installing Extra Apps" ----- Have been staring at this part for 45 minutes now as no progress has been made.
Current situation: Staring dumbly at phone with fading hopes that the process will complete. Wondering how long my Mugen battery will hold out while I wait. Utterly clueless what to do next. Regretting my courage in attempting this.
Can someone help please?
Where did u come up with DARKY ICS it should be Alliance ICS, just recheck because DARKY ICS is for S2 did u flash S2 rom on Note......
bhasg1007 said:
Where did u come up with DARKY ICS it should be Alliance ICS, just recheck because DARKY ICS is for S2 did u flash S2 rom on Note......
Click to expand...
Click to collapse
You make a very good point --- but i can confirm that the zip was the following:\AllianceROM_N7000_ICS-v1.zip
Still hung (80 minutes now) on "Installing extra apps"
mutineer33 said:
You make a very good point --- but i can confirm that the zip was the following:\AllianceROM_N7000_ICS-v1.zip
Still hung (80 minutes now) on "Installing extra apps"
Click to expand...
Click to collapse
Download the Alliance rom again and reflash it, you might have a corrupted rom.
gee2012 said:
Download the Alliance rom again and reflash it, you might have a corrupted rom.
Click to expand...
Click to collapse
Thank you ---- I will try --- but first how do I get out of this hung install --- no button works --- if I just power down or pull the battery out before this flash has finished , will my phone still be usable?
mutineer33 said:
Thank you ---- I will try --- but first how do I get out of this hung install --- no button works --- if I just power down or pull the battery out before this flash has finished , will my phone still be usable?
Click to expand...
Click to collapse
Haven`t you made a cwm recovery (backup) before you went to flash the rom.
If so pull the battery, wait 30 seconds, insert the battery and go in recoverymode and restore your backup. If there is no backup go in downloadmode and reflash a stock rom and reroot this rom and start over.
gee2012 said:
Haven`t you made a cwm recovery (backup) before you went to flash the rom.
If so pull the battery, wait 30 seconds, insert the battery and go in downloadmode and restore your backup. If there is no backup go in downloadmode and reflash a stock rom and reroot this rom and start over.
Click to expand...
Click to collapse
OK will try --- Thank you and "Thanks" added
gee2012 said:
Haven`t you made a cwm recovery (backup) before you went to flash the rom.
If so pull the battery, wait 30 seconds, insert the battery and go in recoverymode and restore your backup. If there is no backup go in downloadmode and reflash a stock rom and reroot this rom and start over.
Click to expand...
Click to collapse
Ok -- and thanks again. The Good News is after pulling and reinserting the battery the phone booted up and into Alliance (it looks fantastic by the way) and appears to be working. A bit scary as the Flash process itself never actually completed. Since I am as of yet unfamiliar with the ROM I have no idea if I am missing anything (mostly just the wall paper and google search, play store, and Nova settings are displayed --- but app drawer has 49 apps and 36 widgets). So now I would be very interested in opinions as to ---
1) Anyway to validate whether EVERYTHING that was supposed to have flashed on this Rom is in fact there? Or can I assume that since the phone has booted up and is working in terms of voice and data connections that I have been lucky and all has gone well after the initial panic?
2) Related to the above should I reflash this ROM over itself to see if it fully completes this time?
Thank you again.
Congrats on getting past the hanging issue - it is always a nervous time when that happens. I would recommend you reboot the phone and check that it starts up again. If all is good, run with current system for a few days. If you start to notice anything wacky then would be the time to reflash ROM.
I'm a firm believer in "If it ain't broke don't fix it" Hopefully your Note will just work now.
Just before reflashing just confirm if you are fully rooted, install root explorer and check if u can paste in system if yes then for safety purposes just flash abyss 4.2 redpill kernel boot into the kernels cwm and perform wipe and reinstall the rom
TempusFudgeIt said:
Congrats on getting past the hanging issue - it is always a nervous time when that happens. I would recommend you reboot the phone and check that it starts up again. If all is good, run with current system for a few days. If you start to notice anything wacky then would be the time to reflash ROM.
I'm a firm believer in "If it ain't broke don't fix it" Hopefully your Note will just work now.
Click to expand...
Click to collapse
Thank you for the feedback. As it stands I Re-flashed again ---- and the flash hung again (this time @ "Cleaning phone". Started over a 3rd time and it went through perfectly.
No idea why the first two attempts failed -- but it looks like I am good to go.
bhasg1007 said:
Just before reflashing just confirm if you are fully rooted, install root explorer and check if u can paste in system if yes then for safety purposes just flash abyss 4.2 redpill kernel boot into the kernels cwm and perform wipe and reinstall the rom
Click to expand...
Click to collapse
Thank you for the suggestion. Per my post above, I think I am sorted out now.
I've got the same problem, are you on speedmod kernel???
Try to mount system and data from the mount menu.
I hope this can help you
I have the same problem... First I installed successfully the ROM but then i messed up something and my phone started to restart and then I went to recovery, Wiped Cache, Dalvik and then Wiped data, then i mount Data, started installing and it went to Installing extra apps and just froze... I hold the power button and it booted alliance rom only with nova launcher... No other launchers... I want to do this again but im afraid if it is going to get even worse Should I try again of doing this? I'm sure that the rom wasn't corrupted because the first time it worked... Shall i try flashing HydraCore and then flash alliance rom again?
EDIT: I've just flashed it again and it worked.. I have no idea what exactly happend, but it doesn't matter - it worked
Hey Guys,
Before i start let me explain that i use to cook roms for my magic, so i know what im doing with this stuff.
Anywho i have been having a weird issue where whenever i flash a rom, it will not boot to either the rom or back into the recovery. my only option is to relock the bootloader and flash back to the stock ruu, and reinstall recovery.. right now im stuck on the stock rom and i hate it!
btw the device is s-off and unlocked bootloader, so wth, if anyone has any advice please let me know!
Did you try reflashing the recovery? Or a different recovery ? had a problem once with my pc antivirus blocking certain files and was causing the zip to be corrupted , just some thoughts
shael said:
Hey Guys,
whenever i flash a rom, it will not boot to either the rom or back into the recovery.
Click to expand...
Click to collapse
All you get is the white HTC screen when you reboot?
What about when you boot into HBOOT, then choose recovery manually?
As you mentioned, you're used to this stuff, so this part probably isnt helpful - do you do the 4 wipes when flashing? (data/cache/dalvik/system?)
I wonder if (even though you are S-OFF), the kernel portion of the rom isnt flashing? This can cause your phone not to boot and just sit there... i.e. your phone hasn't experienced a stockish/insecure kernel flash first, so recovery is having trouble flashing the custom recovery that comes with the rom.
See this thread for more info (it helped another user):
http://forum.xda-developers.com/showthread.php?p=30658376#post30658376
Also - to what Bigtjmc is saying - in the link above, I mention the recovery I use (which has not let me down at all!) Maybe you want to try it (if you're not using it already?)
so, yes i have reflashed the recovery and if i select the recovery from the hboot (as i always do, its starts to load the recovery then reboots too the white screen.... and hmm ill give that link a look and see, because to me the problem seems something with the kernel causing the crashes and corruption with the recovery as well... also weirdly enough the .zip isnt passing the verification.... weird?
shael said:
so, yes i have reflashed the recovery and if i select the recovery from the hboot (as i always do, its starts to load the recovery then reboots too the white screen.... and hmm ill give that link a look and see, because to me the problem seems something with the kernel causing the crashes and corruption with the recovery as well... also weirdly enough the .zip isnt passing the verification.... weird?
Click to expand...
Click to collapse
Try Wildchild's Recovery (by far MY most favorite)
And if it's not passing verificiation, like the other user said check your anti-virus and check the MD5 Checksum to make sure you have a complete good download, wipe all data cache and blah blah blah then with fastboot "fastboot flash boot <Insert kernel file name here>.img
hmm, well in the past ive always flashed kernel with fastboot... its almost like my chip timed out and wont let me flash the kernel anymore :s
If recovery is crashing you might need to relock the bl and run the stock ics ruu to get you back up and running then try n start over , I used the tool kit just this morning for the same troubles and got back where I wanted to be in just a few minutes .
shael said:
so, yes i have reflashed the recovery and if i select the recovery from the hboot (as i always do, its starts to load the recovery then reboots too the white screen.... and hmm ill give that link a look and see, because to me the problem seems something with the kernel causing the crashes and corruption with the recovery as well... also weirdly enough the .zip isnt passing the verification.... weird?
Click to expand...
Click to collapse
This happened to me as well... can't remember what script it was that was running but there is a script that is associated with a rom (vague I know) that is messing up the cache partition. If I remember correctly I also might be associated to the recovery you are using... but I can't remember. Anyway, If you do a fastboot erase cache command from the bootloader and re-flash the recovery of your choice you should be back to normal.
Awesome, thanks for you help guys, unfortunatley i dont have easy access to a pc, so i gotta wait a bit before i can try this... thanks again though
OMG!!!!! you guys are simply amazing, thank you everyone for your help! wiping the cache from fastboot, then flashing stockish kernel, then flashing cwm recovery, then wiping cache, and factory reset, then flashing my rom worked!!! <3
okay, first of all i will say that im sorry if what im writing is full on faulty language. enlgish isnt my best. aaaanuslut i got my brothers old gt n7000 with a broken touchpad and screen for free. i repaired that with 160€ and my brother said that the phone was rooted. i found out he had allso overclocked the device. But after a few restarts to the phone it just said something what i think was in spanish or something "bla bla bla dos sistema". After that came not your old samsung logo, but purple blueish circles just circling. Ant thats it, it would not start. So i read about bricked devices, and as much as i understood i had a soft brick. so i was looking aroun the forum for some easy fixes becasue im totally stranger to this kind of hacking. i finaly found this http://www.youtube.com/watch?v=F97qo1moAR4 and i downloaded custom jb N7000XXLSZ_N7000OPSLS6_N7000XXLSO_HOME.tar. it did work but again after i tried to restart the phone it was stuck.
So since i dont want any custom stuff i think to my self why not stock rom. so i found this http://forum.xda-developers.com/showthread.php?t=1424997. But since i dont like JB as much as ICS i will try ICS. Her is the question: i allready did the factory reset and cache wipe but this instruction says not to FROM ICS.
Warning :
Don't wipe anything from stock ICS recovery
Don't factory reset/Hard reset on stock ICS.
Don't flash any Wipe version of ICS ROM
Does that mean that i have allready gone wrong or does that mean that you have to have ICS on youre phone and then you cant do any of those things? its really confusing and i dont want to fk up my phone.
Did you make a wipe on stock ICS recovery?
zai89 said:
Did you make a wipe on stock ICS recovery?
Click to expand...
Click to collapse
My brother said that he had custom ice cream on it when i first made the wipe and tried jelly
orizont said:
My brother said that he had custom ice cream on it when i first made the wipe and tried jelly
Click to expand...
Click to collapse
can your phone boot to recovery mode now?
zai89 said:
can your phone boot to recovery mode now?
Click to expand...
Click to collapse
Yes i can
flash via recovery phils kernel, (a newer one) reboot in recovery and perform the wipe for new rom option.
That should clean your device good.
Then flash what you want. After that download an emmc check app and check. Shouldnt be needed, but its nice to check.
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
flash via recovery phils kernel, (a newer one) reboot in recovery and perform the wipe for new rom option.
That should clean your device good.
Then flash what you want. After that download an emmc check app and check. Shouldnt be needed, but its nice to check.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Allright, thankyou, since i am new to all this stuff i will try to locate a tutorial. i dont have any idea for instance, what is recovery phils kernel.
at own risk, here http://forum.xda-developers.com/showthread.php?t=1901191. Download zip, keep zipped and put on external sd. Reboot recovery and flash via install from sd option.
Since we are going to wipe latest version will do fine. However if you plan to reflash the original Samsung rom one that is same or likewise version is best to quickly root after flashing rom, so you can flash speedmod kernel (better battery life) after. Find in original dev thread of this forum.
Remember, via factory format on phills kernel recovery(reboot in recovery) you have the option to do a wipe for new rom.
Otherwise on Phills kernel recovery do factory, cache wipe. In advanced dalvik cache, in mounts all(warning take out external sd before so you dont wipe that)
Then your phone is clean, you shouldnt have to wipe efs anyway, so dont tick that option ever in pc odin when flashing rom with odin.
This is the cleanest way to get rid of All leftovers and generally the way to go before flashing any new rom. However risk of loosing photos and whatever you have not backed up. In general backing up is bad as old files/db/etc are put back (risk of unforeseen stuff happening) Check one of my 5 threads for what backups there are. Via my profile you find them
Enjoy!
Sent from my GT-N7000 using Tapatalk 2
Okay, im thankful for all this information, useful stuff, got the PhilZ-cwm6-XXLT6-XSA-5.06.1-signed.zip.
let us know how it went, ok?
OOOKAY! so i finaly did what baz77 described. and rooted with another phils kernel witch i chose after my downloaded rom. Did root it, and after powering down and waiting about 3-5 sec. i started it, and it worked, no more getting stuck on gt n7000 screen and so on. and i also downloaded emmc check app, but unfortunatley it said. Brick bug: YES. Insane Chip.
sorry for double post, how do i delete? all i can do is use edit/delete button but it only edits the post, how can i delte it?
You cant but thats ok.
all n7000 have the brickbug to my knowledge, the test should state if the bug has been triggered, if not then super, if it has, best to secure the broken emmc sectors. Tricky.
I think having it clean now should eliminate earlier issues Enjoy your n7000
Thank you, i will, lately my n7000 has been rebooting randomly, any fix or know issue why this occures?
orizont said:
Thank you, i will, lately my n7000 has been rebooting randomly, any fix or know issue why this occures?
Click to expand...
Click to collapse
not sure how that is happening. Maybe a logcat (logfiles) shows whats happening when it happens. Could be app. Maybe rom issue. Method of elimination counts here.
On safe kernel, try dalvik cache, cache wipes and fix permissions in recovery, reboot and check if reoccurs.
Otherwise, updated versions, clean install I would recommend.
You can check also before with that emmc app if there are bad sectors. I dont expect it but you never know
Okay, its been a long time since i did that stuff. And it worked allirght. i got my phone working and rooted. Great stuff here
Sorry for updating old topic. Since people who have helped me with my phone allready are familiar with my case. I was wisiting a friend of mine in england and after i returned home my phone is f**ked. Everything works okay, but when i turn on mobile data or wifi it instantly freezes. Takes about 15-20 sec. and then phone does an automatic restart which restarting gets into boot loop. I have to hold down bower button to reboot again. When it asks me for sim unlock code, i have to be quick when im inserting it because i need to turn off mobiledata/wifi as soon as ia get my phone running again, otherwise it will freeze and crash again. Can it be somekind of virus or something? Is it most likely that i have to again format and install philz kernel and all that stuff? Thanks in advance.
that would be the best way to start..IMO
I really dont have the time or opportunity to format and reflash, but i guess its really difficult, near imbossible to tell whats wrong with my samsung. Bust still, any other suggestions?
Hi,
- Le 2 X526
- Phone is rooted
I am unable to flash any ROM via TWRP. I've tried multiple ROMs and the phone gets stuck and just restarts midway during flashing (happens during /system extraction).
The issue was happening even with stock ROM which is why I did a factory reset assuming things will be fine. Currently, I have wiped everything via TWRP and the system is empty.
Note: I get a bluescreen for a split second after which the phone restarts.
Please help.
first tell these thing..
which eui version u were using..??
which twrp version you are using
which rom u tried first...?
and was it running or it was also giving bootloop???
Hi,
I was using 5.8.019S (Rooted)
TWRP 3.1.0
The phone was randomly rebooting since 2 days with increasing frequency, which is why I decided to do a factory reset.
But after factory reset the phone was only in bootloop. After this I wiped all partitions and tried to install a ROM.
I've tried AOSP, Lineage, Small EUI and Validus - Same problem in all (TWRP gets stuck halfway during installation and reboots)
Note: I am wiping all partitions before installation.
Shredder333 said:
Hi,
I was using 5.8.019S (Rooted)
TWRP 3.1.0
The phone was randomly rebooting since 2 days with increasing frequency, which is why I decided to do a factory reset.
But after factory reset the phone was only in bootloop. After this I wiped all partitions and tried to install a ROM.
I've tried AOSP, Lineage, Small EUI and Validus - Same problem in all (TWRP gets stuck halfway during installation and reboots)
Note: I am wiping all partitions before installation.
Click to expand...
Click to collapse
You only need to wipe system,dalvik,data and cache then flash ROM then gapps
piku 123 said:
You only need to wipe system,dalvik,data and cache then flash ROM then gapps
Click to expand...
Click to collapse
I am aware of that, but I am unable to install any ROM now. It just gets stuck halfway and phone reboots.
I wonder if the memory has gotten damaged/corrupted.
Can anyone help please...
How about trying an older version of TWRP?
I think the partition table is corrupted. Can someone help me repartition it using adb and gparted?
Shredder333 said:
I think the partition table is corrupted. Can someone help me repartition it using adb and gparted?
Click to expand...
Click to collapse
Did you find a fix? How?
Phone is working after re-partitioning...System space was corrupted.
Shredder333 said:
Phone is working after re-partitioning...System space was corrupted.
Click to expand...
Click to collapse
How you do that man? Im on the same situation :/
Shredder333 said:
Phone is working after re-partitioning...System space was corrupted.
Click to expand...
Click to collapse
Please answer how did you do it. Changing the file system? Please reply.
Follow this guide:
https://iwf1.com/how-to-re-partitio...all-options-included-change-size-fs-type-etc/
https://iwf1.com/how-to-re-partitio...l-options-included-change-size-fs-type-etc/2/
You can permanently brick your phone if not done right. Proceed with caution if you choose to.
Le Echo 2 boot loop issue
Hi All
My phone also gets stuck in boot loop. When i do the charging, it automatically restarts. I tried to clear the data but still, that did not resolve the issue. Now phone even not getting boot properly. Its start booting and after sometimes it restarts again and continue in this loop.
Please help me to resolve this issue. I am new to this so some detailed step will be very helpful.
Many thanks in advance.