Hi,
First, thanks to the few humble people who extended their assistance to fix this issue. If anyone arrogantly answers this thread, I'll hide your profile so I don't have to look at that trash. Some of y' have personal issues. This is why I didn't bother to post anything in the forum, and thankfully found elsewhere assistance. Please put your life in balance and find happiness.
--
This i9100 was a test phone, modified before other phones are modified from stock, or are further modified. So, since there was success with an LG-P990 earlier, the phone was selected to install Rom Manager app from the android Google Play Store. The app should be deleted from there. It damaged the existing CWM Recovery by asking to update CWM as soon as I ran the app. There are no red flags on the App store to not use it on an i9100; an incredibly-common phone, which makes the lack of any warnings whatsoever, more irresponsible. Although 'you have been warned' appears in several threads after-the-fact, those are not helpful.
Second, anyone getting to this level of modifying the phone, should have at least one nandroid backup. Every rooting guide seems to responsibly have guidance to do a nandroid backup, directly after rooting. And then a second one after the custom ROM is installed and all the apps and customizations are finished. In this case, it was with CM 10.1.3 Stable, and Dorimanx kernel 9.43. If there is no nandroid backup, it's an ordinary flash afterwards, and the phone will have to be set-up manually as if a new rom was flashed.
.. After rebooting from the 'Rom Manager' 'Update of CWM', the phone could boot normally, however, booting into recovery, it looked disabled. No option to restore or backup, etc. Just a simple menu and it looked... unhappy. All methods of fixing recovery failed.
Various methods were tried including flavours of ODIN. Flash recovery command from within Android Terminal also failed with (-1) error. Whatever that means... CWM-KitKatCompatible-i9100.tar and philz_touch_6.19.3-i9100.tar.md5 were some of the files used.
Finally, from IRC someone recommended extracting the recovery.img file from philz_touch_6.19.3-i9100.zip, copying recovery.img to the phone, and, opening an Android Terminal on the phone, running 'su' to get it into root mode, and issuing the following command:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p5
.. Quote: "from the guy who heads TWRP's recovery development, i9100 command would be"
and it worked. Only for the i9100; the /dev/block/... location I guess would be different on different models of phones. Someone else can comment.
And this did provide Philz Touch Recovery, fixing the recovery screen boot problem. However the phone would not boot normally anymore, either.
The nandroid backup was restored, and it was a success.
If you'd done even the tiniest bit of research (which was suggested to you months ago, and which you ignored), you would have found out Rom Manager on the S2 is a no-go (this isn't exactly a secret, and I'm understating this; it's actually common knowledge), and you would have avoided this entirely.
So you want a pat on the back for firstly ignoring good advice, secondly stuffing it up, and thirdly then having to go through a bunch of unnecessary crap to fix your phone eh ?
Guess what ? Given your idiocy a couple of months back, nobody gives a ****.
^^^^^^^^^
Thats your profile hidden then T
Don't use rom manager on any Sammy device.
Sent from my GT-I9300 using XDA Premium 4 mobile app
Related
For the record, I searched several times, but did not find an answer that seemed to fit this question. Also, I hope this isn't a ridiculous noob question.
A little background. I have/had a D1 which I rooted and changed ROMs on many times. It was easy. I either used a new .zip file or ROM Manager. I now have a Fascinate that I tried to root with SuperOneClickRoot, but it didn't seem to work as none of the 'root-only' apps would work. I then tried using Odin, but still had the same problem. I successfully used Odin to return to stock, but of course that was annoying and painful. Frustration got the best of me, and I tried again with Odin and was successful. I ran Odin, got to recovery, installed and ran a SuperClean ROM using the .zip file for many days.
Here's where the trouble begins. I decided to try a different ROM, so I rebooted into recovery, backed up my current ROM (or so I thought), and tried to load another .zip ROM. The first one would not load correctly, so I tried another, and then one more. I wiped the data and the cache before each try. None of them worked, so I thought, OK forget this, I'll go back to my backup and stick with it. NO BACKUP (for this phone) was listed under Backup or Advanced Backup. So, now I'm really stuck, because the only ROM I can get to work at all is Kaoscinate (sp?), but it will NOT work with 'root only' apps, like Titanium Backup'. I read a good bit on xda and tried to change with Odin, but I still had no real luck. I was able to get a SuperDark ROM to work, but it is on Android 2.1 and the 'root only' apps still do not work on it. I'm afraid to try another ROM change because of the issues I've had before. I want to go back to the SuperClean ROM. My phone is very important as it's my business line, so monkeying around with this trial and error is taking too long and making me very uncomfortable.
I can easily get to recovery, wipe data &/or cache, and install a new .zip, but will it boot or work for me? I believe the answer is no, so what am I doing wrong?
Will I have to go through Odin to restore to stock and then REDO the Odin root and go to a ROM that way? That is time-consuming and my confidence is low in that method working to get the ROM I want.
Is there some kind of fix for the 'root only' programs to be able to see that I AM rooted? I tried updating Busybox using Titanium, but that didn't do the trick. Plus, this time, I can't even get Titanium to open, because it says I'm not rooted.
Thanks in advance.
sigmtndawg said:
For the record, I searched several times, but did not find an answer that seemed to fit this question. Also, I hope this isn't a ridiculous noob question.
A little background. I have/had a D1 which I rooted and changed ROMs on many times. It was easy. I either used a new .zip file or ROM Manager. I now have a Fascinate that I tried to root with SuperOneClickRoot, but it didn't seem to work as none of the 'root-only' apps would work. I then tried using Odin, but still had the same problem. I successfully used Odin to return to stock, but of course that was annoying and painful. Frustration got the best of me, and I tried again with Odin and was successful. I ran Odin, got to recovery, installed and ran a SuperClean ROM using the .zip file for many days.
Here's where the trouble begins. I decided to try a different ROM, so I rebooted into recovery, backed up my current ROM (or so I thought), and tried to load another .zip ROM. The first one would not load correctly, so I tried another, and then one more. I wiped the data and the cache before each try. None of them worked, so I thought, OK forget this, I'll go back to my backup and stick with it. NO BACKUP (for this phone) was listed under Backup or Advanced Backup. So, now I'm really stuck, because the only ROM I can get to work at all is Kaoscinate (sp?), but it will NOT work with 'root only' apps, like Titanium Backup'. I read a good bit on xda and tried to change with Odin, but I still had no real luck. I was able to get a SuperDark ROM to work, but it is on Android 2.1 and the 'root only' apps still do not work on it. I'm afraid to try another ROM change because of the issues I've had before. I want to go back to the SuperClean ROM. My phone is very important as it's my business line, so monkeying around with this trial and error is taking too long and making me very uncomfortable.
I can easily get to recovery, wipe data &/or cache, and install a new .zip, but will it boot or work for me? I believe the answer is no, so what am I doing wrong?
Will I have to go through Odin to restore to stock and then REDO the Odin root and go to a ROM that way? That is time-consuming and my confidence is low in that method working to get the ROM I want.
Is there some kind of fix for the 'root only' programs to be able to see that I AM rooted? I tried updating Busybox using Titanium, but that didn't do the trick. Plus, this time, I can't even get Titanium to open, because it says I'm not rooted.
Thanks in advance.
Click to expand...
Click to collapse
If it's that important, and you'd like to avoid any trial and error, simply odin your preference of ED01 roms here:
http://forum.xda-developers.com/showthread.php?t=1048380
To test root, simply open terminal emulator (free in market) and type "su" (no parentheses). It will notify you of a superuser request.
find an odin package for the baseband you want like EB01, EC01, ED01, etc (I use an all in one complete deodexed and debloated EB01 package myself) and the newest CWM 3. Odin them both, boot straight into cwm, wipe data/cache/dalvik, install the .zip rom of your choice from sd card and reboot phone. Should work fine, its the way I've done it and I've had few if any problems
edit: most roms like SuperClean, Evil, ComRom, etc are already rooted so there's no need to do anything special to gain root. the hardest part is flashing it correctly
You guys are awesome! Thanks!
If it's that important, and you'd like to avoid any trial and error, simply odin your preference of ED01 roms here:
http://forum.xda-developers.com/show....php?t=1048380
^^This one worked great for me. I seem to have the Samsung things I like (their visual voice mail, their video player, etc.) without the other bloatware.
I do have one more question. You said 'flashing the ROM correctly'. Before, with my D1, that simply meant using RM to 'Load Custom ROM' or rebooting into recovery mode and installing another .zip file. That has not seemed to work on this phone. What is the correct way to load another ROM on these phones.
Again, thanks for the help!!
sigmtndawg said:
You guys are awesome! Thanks!
If it's that important, and you'd like to avoid any trial and error, simply odin your preference of ED01 roms here:
http://forum.xda-developers.com/show....php?t=1048380
^^This one worked great for me. I seem to have the Samsung things I like (their visual voice mail, their video player, etc.) without the other bloatware.
I do have one more question. You said 'flashing the ROM correctly'. Before, with my D1, that simply meant using RM to 'Load Custom ROM' or rebooting into recovery mode and installing another .zip file. That has not seemed to work on this phone. What is the correct way to load another ROM on these phones.
Again, thanks for the help!!
Click to expand...
Click to collapse
Do not use ROM manager at all for anything on the fascinate.
The correct way to flash on fascinate: Download ROM .zip file and place on the root directory or your sd card. Boot into CWM and wipe data/cache/ dalvik cache (dalvik is under advanced) choose install zip from sd card. Install and reboot. First reboot will take 5-10 minutes, so be patient.
Hope this helps.
I have a rooted I717. I have tried to load multiple ROMs through CWM (ICS_CLC5_Alpha, SAUROM_XLA2_RCVII, etc.). However, I get the same message every time I start the flash: E: short write of tmp sideload package.zip (no space left on device). I have used multiple apps to confirm that the phone is rooted and have over 10gb of data available on the SD card.
I have rooted multiple devices, namely my past Captivate, and never had much of a problem. I've never worked with a device that fights me like this before.
Any advice, suggestions, tutorial, etc. would be greatly appreciate.
(I also found an ICS ROM that load through odin here:
http://www.androidlookout.com/install-cyanogenmod-9-galaxy-note/168/
Can anyone with a trained eye verify if this ROM would be stable on the I717)
Thanks.
It does not sound to be like you have ClockworkMod Recovery installed. Are you sure you are not trying to flash under Android System 3e recovery? Can you post a picture of exactly what you are selecting in recovery to flash?
I don't know how trained my eyes are, but I can assure you, if you flash that ROM you linked it will bork your device. That is for the International note (our phones weren't released yet when the article was written).
Yes that's for the international note.
Sent from my SAMSUNG-SGH-I717 using XDA
Here's a screen shot (I believe this is what you're asking for). It says I'm running Recovery 2.5.1.2.
Sent from my SAMSUNG-SGH-I717 using XDA
Screenshot didn't come through, but I do believe that is the Android System Recovery version. You can only flash custom stuff through the ClockworkMod recovery here:
http://forum.xda-developers.com/showthread.php?t=1526431
Use Odin to flash that. Then you will be in a blue recovery that will look like this:
http://dl.xda-developers.com/attach...3fd0/4f7f5e62/9/3/3/4/7/6/20120305_160801.jpg
You can flash your zips from there successfully.
I'll try that tonight. Thanks for the heads-up. The shear number of threads here can be daunting to sort through.
By the way, will I be able to delete unwanted applications after correctly rooting the device without flashing a ROM? (I was able to on past devices. Just curious.)
Hi guys, firstly I'd just like to say I have followed all the protocol that is required on here and been reading and researching/ applying fixes for the past few days now. I have tried to help myself as far as i possibly can but i am still having no luck and i don't think too many people have had the exact similar issue after reading all the other threads that are similar to my issue.
with some of the fixes it is my first time using them as i have never needed to in the past, so bare with me if my level of understanding isn't as great in some departments.
Now onto the issue:
I own a galaxy s3 i9300 and it has been rooted on stock rom since day 1 about a year ago. A few days ago my phone battery died, and when connnected to the charger it had this grey icon with a circle. It wouldn't boot up either so after searching on the net i thought i would listen to the advice of clearing the cache etc etc but this didn't work and neither did the wipe data/dalvik in CWM.
So i reflashed a stock jellybean rom and it worked fine.
It was then at this stage i thought i might as well upgade to a custom rom as every galaxy i had owned before i had done it on, and my current Note tablet is also running custom rom.
I first loaded a stock 4.3 rom and then flashed the slimbean 4.3 with gapps ...and it worked perfectly. I found a couple of issues with the browser which i use a lot so i downgraded to a 4.2.2 version of slimbean with gapps and this made the browser really fast again and all was perfect.
I had been using this for two days or so and everything was smooth, including charging etc until one night it had that same grey battery icon again with the circle and would get stuck booting at the samsung logo.
So as this had happened before i thought i would just flash a stock rom....this is where it all started going mad
Bearing in mind, every flash i always did it properly and wiped cache/dalvik cache and wiped data three times for each one just to make sure as i didnt have anything of value so wanted a fresh wipe each time and didnt need to back anything up.
now before i get flamed i realise i made a huge stupid error in not backing up my efs folder before hand as i had done with every previous phone but because i was under pressure to get it working it skipped my mind totally.
So i flashed a stock jellybean 4.2.2 rom and still bootloop with the EFS not found invalid argument error
i flashed a 4.3
i flashed a 4.1
i flashed a different 4.1
i flashed a different 4.2
i tried loads but nothing worked
so after reading that this would not help as it doesnt touch the efs i looked into fixes that others had done
i tried to follow this http://forum.xda-developers.com/showthread.php?t=2197515
So i downloaded efs professional / adb tool
i downloaded busybox
and cwm was already on the phone but i downloaded philz cm incase i needed that too
now as the phone doesn't turn boot up i can't access anything, i can only access download mode and CWM.
When i open efs professional it says current device offline, turn on allow usb debugging to confirm your phones RSA fingerprint and click ok.
I have no idea what to do about that because i can't get into the phone.
Regarding busybox i have no idea how to get that to install on the phone, i have tried writing some stuff to push it in the adb shell (but because its my first time using adb shell and command prompt i have no idea if i am doing it correctly). Can you install it with odin?
also regarding adb shell i followed the guide http://forum.xda-developers.com/showthread.php?t=2197515 and got into [email protected] and SU....and then when on the phone in cwm i clicked mount efs...and obviously it failed. I went into the log as said and /dev/block/mmcblk0p3 was the file it failed to mount
the thing is everything after that step doesnt work, as i can't create an image of mmcblk0p3 as it says it can't find it as if it doesnt exist.
So im screwed as it effectively is saying i don't even have that file or efs folder i think?
The thing is i never had any issue with losing imei or anything like that at all and this just happpened out of the blue without me doing anything as such
any ideas?.....would be HUGELY appreciative for anyone willing to take the time out and help me with this as i'm not sure i can explore any more avenues on my own with my limited knowledge and at the same time don't want to give up.
PS. I also have access to a galaxy s3 i9305 ....and can possibly try and source another i9300 from a family member IF this helps in any way or makes life easier?
Stickied faqs and guides .
No IME/ EFS
service centre repair is your best choice if you have read and tried the stickied fixes .
Reads like efs partition corrupted and your phone was already suffering with nand memory issues.
There is no substitute for an efs backup, you cannot recreate the unique information it contained.
Take it to a reputable repair centre, they will be able to get it back to normal, but you are still left with why it keeps corrupting -which may require a new motherboard.
Sent from my GT-I9300 using Tapatalk
Mod Edit
Please refer to ,and post in the stickies in the General section.
Thread closed
malybru
Forum Moderator
Hi there
I have a few questions and probably just need to be pointed in some right directions. Would be great if somebody could take the time.
I'm not a developer, but I consider myself quite experienced in modding, mainly CM. In fact, I do it for some other people as well, via an add on a classifieds-website. I don't take much money, but I learn a lot. And I stumble about problems about many different devices and rules I thought existed seem to wrong, sometimes. So I got these questions:
Q1: Please tell me briefly what I can find in which partitition on my phone. "Boot" contains the kernel, right? Does "data" contain just Apps and there data, or anything that I save on the internal storage (like music, movies...)?
Q2: I always thought that a Nandroid would be a 100% insurance for my phone. But recently I read about a device and it said something like "try not to restore stock Gingerbread from recovery if you had some higher version of CM installed, because it couldn't undo some changes that had been made within those". Why is that? Shouldn't a Nandroid be able to restore anything, no matter what? How do I know WHEN it can't restore anything other than from some tutorial?
Q3: I recently read about installing CM on the Xperia Z1 (https://wiki.cyanogenmod.org/w/Install_CM_for_honami). Here it says: "On all 2011 model Sony devices, the kernel will not update when flashed in recovery, so the kernel must be updated via fastboot every time you flash a new build of CyanogenMod". Also they never actually used the recovery to flash anything, or at least not as often as usual. And the used the (****ing unreliable) adb backup method instead of a Nandroid. In total the customRecovery seemed pretty useless! Why is that? How can the recovery not be able to do what it usually does? And what would be a "new build"? Like from CM 12.1 to CM 13?
Q4: Do you thing that modding (especially adb, fastboot) would be better from a Linux distribution, since Android is based on Linux? Cause I had some major issues with adb backup. It showed all variaties of "Not Working" so far...
Q5: The recovery system is working all by itself, right? No kernel, no nothing. (Apart from the bootloader that starts it)
I would really appreciate some help!
Hi!
Finally I got stuck in a boot loop on my Pixel 6 running QPR2.
It's looping after the G animation (vibrates a few times at that point when attached to a PC).
Reflashing the latest QPR factory image (without -w) by using SDK 33.0.3 does not solve the issue.
The ROM was running fine before, but it rebooted due to a faulty custom kernel version and now I'm stuck.
My theory is, that the launcher (nova) can't load and therefore it reboots.
Anything I could do using fastboot?
Never flash a custom kernel on a stock ROM, If not suggested by the dev.
I understand that you flash without wipe?
Done that for years without any issue.
The last version of the custom kernel had an issue and caused reboots.
Not sure if this is the ulprit, but normally that should be solved by flashing factory image without -w.
So the question is: Is there any other option than doing a factory reset?
Sui77 said:
Done that for years without any issue.
The last version of the custom kernel had an issue and caused reboots.
Not sure if this is the ulprit, but normally that should be solved by flashing factory image without -w.
So the question is: Is there any other option than doing a factory reset?
Click to expand...
Click to collapse
If the kernel broke your actually ROM, nope. You could backup the file stored locally via adb in the recovery, but not anything more.
Wipe all is the best, better than have to handle with an hard brick.
Sui77 said:
Done that for years without any issue.
The last version of the custom kernel had an issue and caused reboots.
Not sure if this is the ulprit, but normally that should be solved by flashing factory image without -w.
So the question is: Is there any other option than doing a factory reset?
Click to expand...
Click to collapse
If I were you I'd maybe get some logs and go through them and see if you can find anything that way. Maybe add logs to your op here.
There aren't many ways to backup things nowadays for pixel 6 but what I have used to backup apps + app data that works well when restoring is Neo app from Fdroid store. As far as backing up goes, at this time I've used nothing that is/has been as solid as Neo. I miss the days of just being able to boot one of a few various custom recoveries, making a nandroid backup to a USB thumb drive with my OTG cable and restore it whenever it was needed but things change. Sounds like maybe something was left behind from your kernel install. If you really dislike formatting I'd stay away from whatever you installed here to get in this loop but definitely backup using Neo once you get going again and put your backups on thumb drive or you PC or somewhere other than your device so you can restore them when you need to. I don't flash nowhere near as much as I used to but I used to flash my device(s) many times a day , everyday for many years but I remember years ago on another device I looped and wiped my cache and system and reflashed rom and ended up booting up. But that was another device years ago. Maybe try adb sideloading instead of factory image flash without wiping data. Try that and after it's done installing reboot to others slot and sideload it again... These things probably won't work but you never know until you try. Did you have magisk installed before and not now? Maybe flash stock kernel patched with magisk to both slots if so. Hate to say it but you will probably end up having to format data but idk because I don't know exactly how you installed the kernel "in detail" or exactly what kernel it is or if anything else was changed from before you looped ... No logs...
I've been using Android since the beginning (G1) and I've been tinkering with my devices since back in the Nexus S days on a regular basis and I've found that the best way for to get the help I need is to try like hell to figure whatever it is out myself by searching for the problem I'm having, I mean like really searching, sometimes for hours , sometimes maybe searching for things related to the problem I'm having that show up in my searches, sometimes the answer can be in another devices forum, piecing together bits of info from various places to try and solve whatever it is... etc ... etc... But the best way to get help is do research on it, take some notes, try various things to fix it, then if I still can't figure it out make a post about it here and in op attach every log I can possibly gather from said device, include all the things I tried to fix it with myself "in detail..." My exact installation process, you know like: reboot bootloader, was on slot A, executed ./flash-all.sh for factory image xxxxx, rebooted system ... The more details you provide the more accurate people will be when answering and the more people you will get to reply.. I'm not trying to sound like some asshole or anything at all. Im just speaking what works best here to get answers. Sometimes you just don't get any answers even if you post 18 paragraphs with a chart and a line graph, things you tried, what all you tried it with and links to it all. But anyone here who does this will most definitely stand a much better chance at getting some replies on whatever it is. I sometimes read over on Reddit and Tele groups , sometimes answers can be found that way. Sometimes people just give you the silent treatment.. Even if you do your homework. That's just a thing with anything related to development that happens. I always used to think when I would get no replies that the other guys and gals who know the answer are thinking to themselves, "oh look at this idiot here!" "He clearly didn't graduate from Harvard top of his class with a PhD like we did. " " Such an imbecile!!! " But what could have been going on and more than likely was/is is life , kids, bills, sleep, relationships, covid19, and tons of other things..
Some of this development stuff is a real beech to get and everyone works hard to get it and many aren't too fond of just giving random people answers that took them many sleepless nights to get. But if and when a dev sees someone with a detailed post , things tried.... etc ... etc .. Theyre much more likely to throw some knowledge your way. That's been my experience anyway.
@flash713
Wow, thx for thw write up, appreciate!
I was on latest QPR2.1 with Radioctive Kernel, Magisk installed.
Since the device got stuck in the boot animation, I tried a lot and flashed different factory images using the flash-all method. w/o success.
Also tried the Flash tool in the google website, also w/o success.
When the device boots while it's connected to the PC, it beeps/vibrates 3 times and the reboots.
My guess is that it has problems to load the launcher, Nova was set as standart.
I'm using android since years, tinkering a lot, but I'm not a pro in doing so.
Meanwhile i set up my new Pixel 7 and restored it via Google backup and a few apps by using a SWIFT backup.
Fotos were restored by Google, but all whatsapp pictures are messed up ow, cause the date of restore.
How do I gather proper logs?
Did a last attempt and sideloaded the OTA to both slots...same outcome...
Doesn't magisk have a remove all modules.zip? I mean oriole doesn't have TWRP available yet.
I presume that when it's bootlooping you don't have any ADB?
You did have ADB enabled, right?
Depending on system and setup you may have ADB started by init or started by Android.
Your problem could be as simple as a bad Launcher.
I don't know if the P6 has a UART console. Does it?
Hi Renate,
thx for your reply.
Yes, that is what i thought. The Pixel boots up into the G-animation and then loops 3 times (beeping/vibrating if connected to PC) and than reboots in total.
I think I had something like that in the past when I accidently deleted the launcher apk (don't ask )
Anyway, Nova launcher was set as standart, so the only idea could be to set the genui Pixel launcher as default, but I don't know how to do that in fastboot or adb mode.
Sui77 said:
Anyway, Nova launcher was set as standard, so the only idea could be to set the genui Pixel launcher as default, but I don't know how to do that in fastboot or adb mode.
Click to expand...
Click to collapse
I'm still not clear if you have ADB ever available.
If you do you could:
Code:
adb uninstall com.nova.whatever.launcher
If the /data/data that Nova is using is corrupt or missing it could cause failure.
Android will switch to whatever else belongs to android.intent.category.HOME automatically.
If there is nothing there you can install another launcher.
Have adb (after booting into recovery mode), will report back asap
I habe adbd device connected via recovery/rescue mode, but that's not working.
In bootloader, I can't use adb, no device connected.
Hw can I use adb while the device is not booted up?
Can you mount data in recovery (and it's unecrypted)?
Feeling a bit dumb, but I can only boot into fastboot or into the boot loop, don't know how to mount data in recovery mode (the one with the andoird robot)
When you're in the boot loop you don't get adb even for a few seconds?
This are the last lines of the recovery.log
2 new items by TheMrSui
photos.app.goo.gl
Checked that by opening a cmd and using "adb devices", but nothing showed up
When you're viewing that log, don't you have ADB working then? It says that it is.
I had this weird issue on Raven, first try using android flash tool through a chrome based browser. If that still loops then wipe, and flash an older image. For some reason I had to flash an image from the previous month and that would boot.