Develop Bugs

[Q] Samsung Galaxy Tab i9000 failed to boot and not showing any user screen

Hi Guys,
I was trying to install a custom rom on my galaxy tab.I downloaded Rom Manager from market and was trying to take backup by booting my phone and tried to take Nandroid backup but not able to find that when I rebooted my tab.So i tried to find a app on market by searching "nandroid" and found 3 apps as a search result and I downloaded 3rd app from market.
After that I rebooted my tab and It is not coming up.It is showing samsung startup screen and then screen is active but not showing anything and keep on vibrating in every few seconds.I am not able to see anything on my screen now but I can get reboot screen with options like:-
reboot
clear cache data
wipe out all data
Please let me know what should I need to do to get my tab up and running... Its very urgent...
Thanks in advance

I'm having the same issue w/ my HTC Thunderbolt (ADR6400). I followed the directions and used the files referenced in the forums here. This is the "Easy Flash" app method. I did have the 605.6 software on the device stock from HTC. I was initially not able to get past step one (it would not actually write the files. After trying it about 5 times, it finally flashed and rebooted on its own and installed the old 1.03.605.10 software. It took a long time to finally boot back up, and now every time I try to connect it via USB w/ Debugging Mode on to do steps 2 and 3 it crashes the device and like Survivor's Tab situation, gets stuck w/ the boot-up screen
Is there a way to either A) get around this crashing-on-debugging-mode issue to finish the rooting, or B) restore it to its original firmware? At least it turns on, but I posted in this thread since the solution for him is probably the same as for me (whatever that might be). I've rooted other Linux-derived OSes before (Ie, WebOS 1.4x), and didn't have these kinds of issues. Any ideas would be most helpful to both of us.

[Q] Huawei U9200 Ascend P1 soft-bricked

Hello,
My Ascend P1 seems to be soft-bricked, the phone turns on and I can access CWM Recovery... or so it seems. It all started when my phone's battery died and right after that, I put it to charge and left it alone for around 4 hours. When I came back, it hadn't charged at all, I tried to turn it on and it would get past the Huawei Logo and pass to the LiquidSmooth ROM launcher screen, however, it would just freeze and restart the phone. It fell in what I heard is called a bootloop.
I did some research here and there and found a lot of tutorials about how everything is done from the scratch. I did the basics, clear cache, dalvik-cache, factory-reset, etc, but when I tried to install the ROM from the SDCard, the installation finishes way too fast (15 seconds at most), almost as if it did nothing (which I believe it's true).
I also tried to install a new recovery through a tool called Shaume, it seemed to be working at first; I installed it (which took probably like 3 seconds to install), it launched the "new recovery" and everything about seemed to work just fine, however, when I first did this I had forgotten to put the ROM in my SD Card so I took it out, put the ROM in it and to make sure, I restarted the phone. After it restarted, it went back to the old CWM I had installed (this one has no touchscreen features) and it seemed as if everything I had done was for naught.
I just don't know what to do anymore. I tried to take a look at the logs after trying to format /data, /cache and such, and the most notable thing I saw there was "rm: can't remove '/data/dalvik-cache/' read-only file system", this same "read-only" happened referring to some of the applications I had installed before.
I am no expert in this matter, as I myself have never even rooted/flashed ROMs (the phone was already rooted/flashed when I got it). At least, through all of the research I've done it seems that as long as the phone is able to get to the Recovery, it's not something that cannot be fixed.
I really hope you can help me fix this.
Thanks in advance!

I'd try to Flash Stock firmware before trying again.
I am requesting to have this thread move to the right forum so that the right experts may be of help.

Oh, I'm really sorry. I'm totally new in this forum and thought this was the correct section for this thread.
Sorry, again. And thanks for your help.

I like some solution?
SairoJ said:
Oh, I'm really sorry. I'm totally new in this forum and thought this was the correct section for this thread.
Sorry, again. And thanks for your help.
Click to expand...
Click to collapse
I tried with all tutorials and I have not accomplished anything

[Q] Galaxy nexus bootloop into cwm

Hello guys, this is the first time I am posting anything so if I am doing anything wrong, sorry just say what it was and I will try to correct it. Well due to some unfortunate events I needed to get my GSM Galaxy nexus running again, I rooted it a long time ago when I was trying to get into roms and mods, but I had to leave that aside due to some other projects that demanded a little more attention at the time. Since my device was having some battery problems I thought that by updating it the problem could be fixed, at the time it was running CyanogenMod 10.2.1 if my memory is right. I went into the update tab under settings in the phone itself and tried installing CM11 from there. the phone prompted me if I would like to do it and I hit yes, it booted into CWM and it proceeded with the installation. But then it gave the status 7 error and the instalation could not be completed (from what I've read this problem happens when the device is not the one compatible with the Rom being installed, I went in the script and checked it, but it was maguro the same I had used for some time , since my device is a GALAXY NEXUS GSM model. Well I went to bootloader again and then do CWM and found the Rom I was using earlier (the CM 10.2), I flashed it and it was all "nice" and working but the battery was discharging way too fast and I tried it again but this time, for some reason (some times I do stupid things) I deleted some folders from the inumerous 0/ folders my device was accumulating and the CM 10.2 was among them. After I that I tried flashing another CM 11 Rom, an older one to try and see if it went well. sigh.... It did not. The same problem occured and now I cannot flash the working Rom. The Phone boots but it does not get past the google logo and then turns off and boots again going directly into CWM , I tried using Wug Fresh's Nexus Root Tollkit, but since I can't go into the settings of my phone I can't configure the drivers properly and if I try to use the Flash Stock + Unroot option with soft-Bricked/Bootloop option checked it returns that a fastboot device was not found. And hence I can't do anything else. Well I don't know what to do and my knwoledge is fairly limited, so anything can help. I have already searched some solution in other treads but none have given results. Does anyone can guide me where to look or some thing I should do?
Thank you very much for any time spent helping.

Hi,
I will have your thread moved to your device section so the experts who own your device can help.
Good luck!

G3 won't boot @all anymore [Resolved]

So I've bricked my phone. And I can't make it work. Yesterday I finally had some time to thinker with the phone and decided to install Fulmics Rom 6.0. I had already downloaded it a while ago but first now had the time to install it. I made a post in the Fulmic's thread but with their new 6.5 fulmics just out, so my post got berried so quickly so I got no replies.
I started in TWRP with doing a backup, then a wipe and then started the install.
It seemed install was going fine, I even got the Fulmic's GUI midways and selected appropriate model, D855. I tried to keep things as vanilla as possible and chose to not uninstall anything and keep stock temperature throttle back.
But when the install completed I got one error: set_metadata_recursive: some changes failed
Phone wouldn't boot. I had however made a backup before I started and I was able to restore from backup from within TWRP.
Then phone booted and it seemed all was fine. But as I had my mind set on the Fulmics ROM I had one more go, just ti be sure I didn't mess up and chose something bad in the Fulmic install GUI. Also I did a wipe first, then I wiped the cache/dalvik as I once read that could make install easier. And result same as before. set_metadata_recursive: some changes failed.
Tried to reboot but I get flash screen with LG loge and powered by android on the bottom, and then when screen changes to only LG logo it gets stuck'd. No matter how long I wait, and I tried to wait for hours remembering wiping dalvik/cache makes boot take longer time. Stucked on the boot load. Notification light changes from green to blue. And the Lg logo is there.
Worst part is that now I can't even restore it to my backup from yesterday.
Here is my phone:
Lg G3 D855 16 GB 2 GB RAM
Android 6.0 stock LG update.
TWRP 3
Rooted
For now I would settle for a working phone. That is my main priority. Truth be told I got scared now and I don't know if I will take my chances putting a custom ROM onto the phone. After all my android 6 was working nicely, phone was rooted and adaway was working nicely. I guess I got greedy and wanted more

It would be very nice if people could take things very basic, like if I am to do certain things in TWRP don't assume I will understand unless you go into details. Been struggling for hours upon hours now and my mind is mush and concentration was lost a few hours ago. Yet I need to keep at it as I can't be without a working phone tomorrow. For instance in the TWRP under tab advanced > sideload what can I try there to make phone boot?
If I have left out any important for you to help pls just ask and I will reply as fast as possible. Any and all tips and pointers will be much obliged.

joppy said:
It would be very nice if people could take things very basic, like if I am to do certain things in TWRP don't assume I will understand unless you go into details. Been struggling for hours upon hours now and my mind is mush and concentration was lost a few hours ago. Yet I need to keep at it as I can't be without a working phone tomorrow. For instance in the TWRP under tab advanced > sideload what can I try there to make phone boot?
If I have left out any important for you to help pls just ask and I will reply as fast as possible. Any and all tips and pointers will be much obliged.
Click to expand...
Click to collapse
Downgrade to twrp 2.8 and flash again hope you are good too to go....

For me , if i have problem.
Replace sdcard , format data on twrp and flash .kdz (not after 30x.0426.kdz) , usually LGup can made download mode it self.
If can booting , make temporary root and get twrp.

Ok I had TWRP v2.8.7.0 laying around. I've used it before with success, so I know it works with my Lg G3.
But still not possible to boot.
I will try to read up on the .kdz as I never even heard of that before. Maybe if I am lucky that will save the day.

Hehe what do you know. TWRP v2.8.7.0 worked!
I dismissed it too fast, turned out it didn't get stuck'd on boot, boot just took a while because I had wiped everything.
Now I can see android is upgrading apps, and also when I think back to the first reboot with twrp v2.8 it was fulmics logo on the bottom part of the screen not android I guess my mind did not pay any attention as I was truly expecting to be stuck in boot loop this time too
Fingers crossed it is working now, I guess I didn't pay much attention when I tested twrp v2.8 and pointed to the fulmics ROM 6.0 and it seems it will work whoha

Finally I've got a working phone, and I also got Fulmics 6.0 as I sat out to get.
Don't know what went wrong or what caused the boot loop, but twrp v2.8 seemed to be the working solution.

IT seems everything works except I lost root. Which is fine for now, I will root another day.
Now I just need to use the dang phone

Deleted for your own safety

Btw, as the phone must be rooted to install custom ROM's it does seems strange that phone after installing Fulmics 6.0 appears to NOT have root, according to RootChecker. Could it be that the custom ROM is confusing RootChecker or did root somehow get revoked?
Is there a manual way I can check to see if phone is rooted? Cos there is, terminal
I took the chance tp get the latest KingRoot v4.9.6 over my previous v4.5.6. And run the APK.
Seems there must have been some issues with SuperSU, I had v2.54 and BETA v2.65. None of them kept root after install.
Found the latest stable that was superSU v2.78 and that fixed my issues.

TWRP ver 3.x messed my phone up too. Thought I had a good EFS backup, but when I needed to restore it, it didn't work. I will not be using ver 3.x again for a long time. Ended up losing my IMEI because of it.

Problems with rooting Galaxy S9 (Android 10 Exynos SM-G960F)

Hi, this is My first post here, so be gentle.
My old Oneplus died and I bought a used Samsung Galaxy S9. I tested the phone with an original OS and it worked fine.
Yesterday I decided to root it (there are a few features that need root and I need those features almost daily). I searched for information about the procedure (this wasn't My first root) and found a few threads where this guide was suggested:
How to Root Samsung Galaxy S9 and Galaxy S9 Plus (Exynos)
Do you want to root your Galaxy S9/S9 Plus flagship? Well, you just landed in the right place for the job. This tutorial will help you install TWRP recovery and root Samsung Galaxy S9 and Galaxy S9…
www.thecustomdroid.com
Long story short: I followed those instructions and managed to root my S9. It booted up as it should and everything was working fine. I used Magisk V25.0 and root checker informed that the phone was rooted successfully.
Today I decided to debloat it and after that, I would start to use it as my main phone.
I ran across many threads that suggested using the "ADB + Fastboot" method for debloading the device. At this point, I started to feel uncomfortable because I had some issues with ADB back in the day when I was rooting my Oneplus. I decided to try it and guess what - it didn't work. I still don't know why, but ADB fastboot wasn't able to find my S9. I double-check that everything was as it should be, usb-debugging was ON and my PC did see my phone when connected to the PC via USB cable.
So I gave up on that and decided that maybe I'll just shut those unwanted apps down from the phone's settings (settings ---> apps etc).
At this point, I power off the phone. Just a basic thing to me when sleeping or something like that.
Now, the phone is in bootloop.
I can boot in the TRWP mode and flash magisk/wipe data etc. but nothing seems to help. It won't boot to OS. I've tried to root it again with the instructions above and everything went fine, but bootloop stays. I've wiped cache partition and performed a factory reset - did not help.
Can someone help me...? Is there a way to flash stock OS or somehow get the device work again? My experience with rooting is low, but I've successfully rooted five phones before this. I've experienced a few bootloops before, but those were my mistakes that were fixed with re-flashing magisk or something similar. Now I simply don't know what is the issue. =(
PS. This is a great forum and I've found tons of help from the XDA forum. Thank you to everyone, who has shared his/her information and helped with smartphones in the past! Great society.

Slerba said:
Hi, this is My first post here, so be gentle.
My old Oneplus died and I bought a used Samsung Galaxy S9. I tested the phone with an original OS and it worked fine.
Yesterday I decided to root it (there are a few features that need root and I need those features almost daily). I searched for information about the procedure (this wasn't My first root) and found a few threads where this guide was suggested:
How to Root Samsung Galaxy S9 and Galaxy S9 Plus (Exynos)
Do you want to root your Galaxy S9/S9 Plus flagship? Well, you just landed in the right place for the job. This tutorial will help you install TWRP recovery and root Samsung Galaxy S9 and Galaxy S9…
www.thecustomdroid.com
Long story short: I followed those instructions and managed to root my S9. It booted up as it should and everything was working fine. I used Magisk V25.0 and root checker informed that the phone was rooted successfully.
Today I decided to debloat it and after that, I would start to use it as my main phone.
I ran across many threads that suggested using the "ADB + Fastboot" method for debloading the device. At this point, I started to feel uncomfortable because I had some issues with ADB back in the day when I was rooting my Oneplus. I decided to try it and guess what - it didn't work. I still don't know why, but ADB fastboot wasn't able to find my S9. I double-check that everything was as it should be, usb-debugging was ON and my PC did see my phone when connected to the PC via USB cable.
So I gave up on that and decided that maybe I'll just shut those unwanted apps down from the phone's settings (settings ---> apps etc).
At this point, I power off the phone. Just a basic thing to me when sleeping or something like that.
Now, the phone is in bootloop.
I can boot in the TRWP mode and flash magisk/wipe data etc. but nothing seems to help. It won't boot to OS. I've tried to root it again with the instructions above and everything went fine, but bootloop stays. I've wiped cache partition and performed a factory reset - did not help.
Can someone help me...? Is there a way to flash stock OS or somehow get the device work again? My experience with rooting is low, but I've successfully rooted five phones before this. I've experienced a few bootloops before, but those were my mistakes that were fixed with re-flashing magisk or something similar. Now I simply don't know what is the issue. =(
PS. This is a great forum and I've found tons of help from the XDA forum. Thank you to everyone, who has shared his/her information and helped with smartphones in the past! Great society.
Click to expand...
Click to collapse
I manage to solve this all by my self.
I flashed to stock firmware using frija and odin. After flashing updated all the apps and rebooted couple of times (just to be sure that phone works). After that flashed TWRP with odin, rebooted to recovery and rooted with Magisk (followed step-by-step guide fron xda forum).
Now this works like a dream.