Related
good day. may i ask if sgt bootloader patching is supported in version P1000DXKM1? that is the current version of my tab and i want to install a custom rom. thanks
appletech said:
good day. may i ask if sgt bootloader patching is supported in version P1000DXKM1? that is the current version of my tab and i want to install a custom rom. thanks
Click to expand...
Click to collapse
Get the patcher app and it will detect automatically
Hello
On this thread > http://forum.xda-developers.com/showthread.php?t=888071
The developer say DO NOT USE THIS ON THE GINGERBREAD RELEASES ! THE SAMSUNG GINGERBREAD RELEASES DO HAVE SIGNED BOOTLOADERS, BUT THEY ARE NOT LOCKED. In other words, you can still flash custom kernels and such, and the bootloader patch will only break things, not fix them.
Yes, in red.
Unfortunately I've do it (wasn't specified on the tutorial where I have found the application, anyway).
No big problem, Tablet still booting, but the tab boot whit some coloured wire on screen, like it gonna crash and something bad gonna happen, it look like it's broken. But after that, finally, Android is loaded, and everything seem ok.
But well, when I have load the application on my device and run it the 1st time, it seem it have do a backup of original bootloader.
So, any way to replace patched bootloader whit original? Or, tell me if there's no need because I will flash my tab whit Stock FW and after that Kratos ROM (and maybe it will reflash the bootloader to original). Exactly what will be flashed is:
Rom Stock V5 (001001-GB-stock-safe_v5
002001-Overcome_Kernel_v3.3.1.tar
ROM Overcome 3.1.0 KRATOS Wipe edition
In this order, all with Odin I think.
Oh and yes, download mode is ok, but recovery one isn't (I mean, at least I can't see it if it's work or not when I boot in this mode, because of the weird coloured lines).
Ok, I've re-flashed whit stock gingerbread ROM (like my tab was a Froyo one or else), bootloader erased whit the original signed one, everything is fine
So i havent been able to install any miui roms in the past couple of days idk y i use to be able to install them but after i installed cyanogen's 7.0 i cant install any of them i really miss miui i just wanted to test out 7.0 but know i cant everytime i flash a miui rom i always get stuck on the boot and it just keeps rebooting so if any one can help me i will appreciated it thx
Just going off the top of my head, I had the same problem but I think I was able to install MIUI ROMS by downgrading to Froyo before trying to install any MIUI ROMs.
I'm no expert but I assumed it was a Gingerbread-vs-Froyo thing and that MIUI being based on Froyo (until the recent releases) somehow required you to be on Froyo before installing them. Cyanogen 7 is Gingerbread so that's where my thinking came from.
Anyhow, it's worth a shot to try downgrading first.
hulksmash said:
Just going off the top of my head, I had the same problem but I think I was able to install MIUI ROMS by downgrading to Froyo before trying to install any MIUI ROMs.
I'm no expert but I assumed it was a Gingerbread-vs-Froyo thing and that MIUI being based on Froyo (until the recent releases) somehow required you to be on Froyo before installing them. Cyanogen 7 is Gingerbread so that's where my thinking came from.
Anyhow, it's worth a shot to try downgrading first.
Click to expand...
Click to collapse
I can flash a MIUI ROM of any type, but only Froyo versions of it actually work without fatal flaws. My problem is that the calibration settings force closes upon bootup and then NOTHING will install. I'm stuck with the basics, which is unacceptable.
On each download/install it goes into a soft reboot at install of the app.
hey guys i just got my nexus one 2.3.3
im confused what 2 do first
root, unlock bootloader
what 2 do first?
and i preffer to do all these things WITHOUT adb, bcoz adb never works with me
You can't unlock bootloader without ADB (or actually without fastboot, but if you can't get ADB to work, then you probably won't be able to get fastboot to work - since they work the same way).
My suggestion is - do nothing. At least until you'll be able to follow one of the guides and get ADB and fastboot to work. Then you can decide yourself, whether you want the bootloader unlocked or not, and how will rooting benefit you.
what are the benefits of unlocked bootloader?
i just wanted it to get it rooted and flash CM7 on it
It has been discussed a lot, please search to get A LOT of answers.
In a very short version, the benefits are:
Safe radio updates (using fastboot)
Ability to flash whatever you want whenever you want - which is, permanent ability to have root access, regardless of the currently used OS.
but is it possible to flash CM7 rom without unlocking bootloader?
whenever i boot my nexus one, there is this little lock icon on the bottem that is "unlocked"
is my bootloader unlocked?
shiyou said:
but is it possible to flash CM7 rom without unlocking bootloader?
whenever i boot my nexus one, there is this little lock icon on the bottem that is "unlocked"
is my bootloader unlocked?
Click to expand...
Click to collapse
If there's lock icon at the bottom of boot splash screen, it means the bootloader is already unlocked. Is it used one?
yes its used, i guess that guy alrdy unlocked it for me
another problem
i have serius wifi issue, its different from the other wifi problem
if i connect to my wifi its authenticating, then disabled
i dont even go to sleep its just says disabled after authenticating, i tried reconecctint but same things happens again...
i installed wifi fixer but that doesnt work either
also, my 3g drops after 4 sec and i cant get it to work afterwards
Flash a new ROM, wipe your data, and try.
Repeat.
If the problems will still persist - they're in HW and you can't do anything about them.
i tried factory reset but didnt work...
This is exactly the reason why I suggest not touching your phone.
You either don't understand what exactly I'm guiding you to do, or don't understand the difference between various maintenance/repair operations. Flashing a new ROM and wiping user data from custom recovery ISN'T the same as doing "factory reset" from within already-installed ROM. Flashing 2 ROMs with different base (for example, lightly modified stock and CM7, or CM7 and MIUI, etc) introduces enough difference on the SW size to (almost) make sure that any problem which persists in both new ROMs, is coming from HW.
In any case, I suggest either waiting for someone with much more patience than myself (which isn't hard - patience isn't one of my strengths) to explain you some basics that you're not willing to learn yourself by reading, reading and some more reading, or to give your phone to someone who knows what he's doing.
dude....
i rooted and flashed many roms b4, this isnt my first android phone
i just got confused data wipe with factory reset....
Ok well now I need to know if you have a custom recovery, if so then just 5X wipe plus 3X system wipe and flash a new ROM, if not then do you have root access if not I'll walk you through the process.
shiyou
You are in good hands with Dude
Couple points:
Don't use Clockwork Mod 3.+ as recovery--which seems to be your next step--get a lower version
I prefer Amon_Ra 2.2.1 for my recovery
BACKUP phone (NANDROID) as soon as you get the recovery
Look thru Cyanogen thread from OP page and last few dozen pages
Cyanogen flashes a little differnet with having to flash gapps separate and flashing Dark Tremor's a2sd after each Nightly flash
i know how 2 root,flash,wipe, nandroid and all
i did it many times b4
i think i wont use nightly builds, but a stable? or RC?
which should i take?
How about cm7.1 RC1 that is the latest version of cyanogen mod.
rugmankc said:
shiyou
You are in good hands with Dude
Couple points:
Don't use Clockwork Mod 3.+ as recovery--which seems to be your next step--get a lower version
I prefer Amon_Ra 2.2.1 for my recovery
BACKUP phone (NANDROID) as soon as you get the recovery
Look thru Cyanogen thread from OP page and last few dozen pages
Cyanogen flashes a little differnet with having to flash gapps separate and flashing Dark Tremor's a2sd after each Nightly flash
Click to expand...
Click to collapse
why not clockwork recovery 3? the cyanogenmod rc1 states that i need that?
should i use gingerbeak? im on 2.2.3 and install the recovery afterwards?
ok i rooted it with gingerbreak and flashed clockworkmod recovery on it
after that i went into recovery and couldnt find nandroid backup so i rebooted again
i tried to make a backup via rom manager and it ended up with a "!" icon
i tried to go into recovery again and again i got the "!" icon
I don't know anything about Gingerbreak
But, on CWMod 3.+, it has been unstable for a lot of people--I don't recommend it
If you have Rom Manager--flash something like 2.5.1.4??
Still recommend Amon_Ra
I am not sure, but if you get the exclamation, you may not be rooted
If you are experienced at flashing, I would as another poster suggested--get to know your phone and study hard info from the Rom threads you want to try before trying.
What color was recovery--did it say ClockWork
I don't think you will see the name Nandroid in Clockwork--just Clockwork backups
A couple more suggestions, if you want
Back up sd card regularly--you will lose it on occasion--if you need to reformat it, use sdformatter outside of phone
Partition sdcard with zero swap
Wipe all (data/caches) multiple times before flashing new rom, including System
I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Jeffril said:
I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Click to expand...
Click to collapse
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
NoDze said:
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
Click to expand...
Click to collapse
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Jeffril said:
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Click to expand...
Click to collapse
Okay, This is SFSP by @sgspluss which is a pretty fast, stable and battery-friendly slimmed down version of stock ICS. It is available for both Old and NewBL, so you might want to try that first. This is AIO Toolkit. I know that you've used it and bricked your phone, but try again, and for the love of God install the nvflash drivers because most people skip that part. You have to do it manually and if you're running Windows 8 you need to disable Driver Signature Verification. But yeah, you switch bootloaders with this.
Does anyone know of a stock miui rom for the Spes that has been debloated of ads and other crap and optimised? Don't mind whether it is a recovery rom or needs to be flashed with fastboot (or miflash).
I'm currently on v13 Android 11 the global version, quite happy to remain on that.
Can someone provide a link to the rom?
Thanks.
Look here: https://xiaomi.eu/community/threads/miui-13-stable-release.64441/
I have tested a lot of roms, and in the end I installed the official one and removed software through adb, today I don't have any bugs or strange problems, besides that I can use the camera in its entirety. I got bored with the custom ones, some games don't run, others are terrible and at the moment there is no fix for this.
Microsheepcl said:
I have tested a lot of roms, and in the end I installed the official one and removed software through adb, today I don't have any bugs or strange problems, besides that I can use the camera in its entirety. I got bored with the custom ones, some games don't run, others are terrible and at the moment there is no fix for this.
Click to expand...
Click to collapse
Ditto, I always appreciate the custom roms and appreciate the efforts developers go to because there are a lot on here that do nothing but complain about custom roms, however I think I'd prefer a stable daily driver. There is no sign of the kernel source being released which would be a big help for the devs.
I've just finished flashing the stock rom and will go about debloating. There are a number of "safe to remove" lists for miui roms so I will get to work.
Thanks the replies guys.
maritimesbob said:
Ditto, I always appreciate the custom roms and appreciate the efforts developers go to because there are a lot on here that do nothing but complain about custom roms, however I think I'd prefer a stable daily driver. There is no sign of the kernel source being released which would be a big help for the devs.
I've just finished flashing the stock rom and will go about debloating. There are a number of "safe to remove" lists for miui roms so I will get to work.
Thanks the replies guys.
Click to expand...
Click to collapse
Hi, may I ask how did you flashed stock ROM? I recently tried to flash 13.0.5 A12 on mine through TWRP, it probably refuses to boot because after the ROM has finished flashing I flashed TWRP next. I also know the fastboot + miflash method but everytime I do it, it gives me anti rollback check error
I downloaded the miui.eu rom which is debloated and allegedly more optimised. I went back A11 the same as I had before I unlocked my bootloader. I flashed the fastboot version and used the bat script inside the zip to flash it.
Alex Zander-kun said:
Hi, may I ask how did you flashed stock ROM? I recently tried to flash 13.0.5 A12 on mine through TWRP, it probably refuses to boot because after the ROM has finished flashing I flashed TWRP next. I also know the fastboot + miflash method but everytime I do it, it gives me anti rollback check error
Click to expand...
Click to collapse
Ok, that's strange, it shouldn't give an antirollback error when you have the same version of android and miui.
Try again with myflash
But surely when flashing the official rom by twrp you damaged something, if I remember correctly the twrp of spes does not have support for flashing a stock rom, even less if it goes as an update.
Anyway, if you want to make your rom boot, try taking the boot.img out of the fastboot rom and flashing that boot.img to your phone and see if it boots.
Microsheepcl said:
Ok, that's strange, it shouldn't give an antirollback error when you have the same version of android and miui.
Try again with myflash
But surely when flashing the official rom by twrp you damaged something, if I remember correctly the twrp of spes does not have support for flashing a stock rom, even less if it goes as an update.
Anyway, if you want to make your rom boot, try taking the boot.img out of the fastboot rom and flashing that boot.img to your phone and see if it boots.
Click to expand...
Click to collapse
My first guess was that it was because at that time I was on an Android 13-based custom ROM (Pixel Experience Plus 13 and CrDroid 9.0), but I was proven wrong after I flashed PE+12 shortly before trying MiFlash. Because it gave me the same error (Anti-rollback check)
Oh, I actually tried the flash-stock-ROM-via-TWRP method after I tried MiFlash method, so I doubt that's the issue. But all I can say is a few days ago I flashed 13.0.5 A12 firmware (latest at the time of writing), so could that be that issue?
I might wanna try what you said, thanks for the suggestion. But for now, I'm on EU and may stay for a few months
Alex Zander-kun said:
My first guess was that it was because at that time I was on an Android 13-based custom ROM (Pixel Experience Plus 13 and CrDroid 9.0), but I was proven wrong after I flashed PE+12 shortly before trying MiFlash. Because it gave me the same error (Anti-rollback check)
Oh, I actually tried the flash-stock-ROM-via-TWRP method after I tried MiFlash method, so I doubt that's the issue. But all I can say is a few days ago I flashed 13.0.5 A12 firmware (latest at the time of writing), so could that be that issue?
I might wanna try what you said, thanks for the suggestion. But for now, I'm on EU and may stay for a few months
Click to expand...
Click to collapse
Always that I need as a base a stock ROM flashed, I "simply" use the fastboot commands that are inside the ROM, I open my ADB/fastboot CMD/terminal, and drag and drop the flash_all.bat file while in Windows or the flash_all.sh file while on Linux. This method allows to me, to can follow the process while the scripts are running, and search for issues (if there are some)
As per the TWRP flashing the stock ROM, it worked fine too. You just need to flash the ROM, then boot to recovery once, you'll find the stock one, then format data from it, then you are ready, either to go straight to system, or if you prefer have TWRP (or any custom recovery), go to fastboot and follow the method to boot to, and then flash it permanently to the ramdisk.